Cybélia Forge : your working databases
Completed
The project board : /atelier
19 Views •Tasks : /atelier/tasks, /atelier/db/{db}/board and /tasks/new
17 Views •My changes : /atelier/db/{db}/changes and /changes/scan
28 Views •The project lead and its actions : /atelier/db/{db}, /send, /note, /studio/init, /action/{name}
17 Views •The go-live : /atelier/db/{db}/production/status
16 Views •The overview : /dashboard
31 Views •Opening my ERP : /open/{db}
30 Views •My changes : /atelier/db/{db}/changes and /changes/scan
28 Views •The vocabulary of Forge
27 Views •Both sides before deciding : /bases/rapatrier/comparaison
26 Views •My subscription's capabilities : /reglages
26 Views •Who it is for
22 Views •Help and glossary : /help
21 Views •The project board : /atelier
19 Views •Creating a test database : /forge/new
20 Views •Asking for help : /tickets
19 Views •Your first sign-in : /onboarding
18 Views •A database's record : /forge/db/{db}
18 Views •My team : /team and /team/add
18 Views •Why this portal exists
18 Views •Adopting a copy : /bases/{db}/adopter
17 Views •Tasks : /atelier/tasks, /atelier/db/{db}/board and /tasks/new
17 Views •Choosing where the copy lands : /bases/rapatrier
17 Views •The feature catalogue : /playbooks and /playbooks/{feature}
17 Views •Install, follow, remove : /install, /status and /uninstall
17 Views •The project board : /atelier
Where the ERP changes shape
The workshop is the part of the portal where you stop consulting and start transforming. Here you decide a field is missing, you try it, you note it, you put it live. This page is its threshold.
Choosing a database
The heart of the page is a grid of cards, one per accessible database. Each card carries the database name, its label, working database, test database, sandbox, its last update, and three buttons: Design my tool, Tasks and Changes.
A database marked "Parked" shows an amber badge: it is under notice for lack of use. Opening it is enough to keep it.
The state of your customisations
A box tells you whether your customisation package already exists and what it holds: how many models, how many screens. It is the bag in which all your bespoke changes accumulate, and it is what will go live when the day comes.
A project lives on a database, never in the abstract. If no database is available to your account, the page says so and offers to open a ticket, rather than showing an empty table with no explanation.
What comes next
Once a database is chosen, every workshop screen shares the same tab strip: the chat with the project lead, the task board, my changes, the go-live. You move between them without ever changing database.
Yanis opens this page on Monday morning. He looks at the tasks first, then moves on to the changes. Camille only opens it on go-live day.
In closing
The workshop is the only place in the portal where you transform rather than consult. Everything there starts with the same step: choosing the database you work on. Check its label before going further, it tells you what you are risking.
Commenting is not enabled on this course.