Cybélia Forge : your working databases
Completed
The overview : /dashboard
26 Views •Opening my ERP : /open/{db}
26 Views •My changes : /atelier/db/{db}/changes and /changes/scan
25 Views •The vocabulary of Forge
24 Views •Both sides before deciding : /bases/rapatrier/comparaison
23 Views •My subscription's capabilities : /reglages
23 Views •Help and glossary : /help
18 Views •Who it is for
18 Views •Creating a test database : /forge/new
17 Views •Asking for help : /tickets
16 Views •The project board : /atelier
15 Views •A database's record : /forge/db/{db}
15 Views •My team : /team and /team/add
15 Views •Choosing where the copy lands : /bases/rapatrier
14 Views •Delete, restore, clear away : /bases/{db}/delete, /restore, /forge/discard/{db}
14 Views •Tasks : /atelier/tasks, /atelier/db/{db}/board and /tasks/new
14 Views •The go-live : /atelier/db/{db}/production/status
14 Views •The feature catalogue : /playbooks and /playbooks/{feature}
14 Views •Install, follow, remove : /install, /status and /uninstall
14 Views •Your first sign-in : /onboarding
14 Views •The overview : /dashboard
The portal's home screen
This is where you land after every sign-in. It does no work: it shows. At a glance you know how many databases you have, how many tickets are open, and whether a go-live is waiting on a decision.
The first time
A welcome box opens on your first visit and sums up the journey in four steps: explore a demo, create a database, switch on business features, then run a customisation project. One button closes it and it never returns. It does nothing else.
The strip of figures
Three pills: how many databases, how many tickets are still open, and, only when there are any, how many go-lives are pending. At Les Ateliers du Vent d'Ouest, Camille usually reads "3 databases, 1 open ticket" and has nothing else to check.
My Cybelia services
A row of cards that open your other services in a new tab: your production Cydoo ERP, your mailbox, the Cybelia AI and the Security Center. It is a shortcut, not a dashboard for those products: each has its own.
What the overview does not do: it changes nothing. No button on this screen touches a database. It is a starting point, and it is safe.
Your databases, as cards
Further down, each database appears as a card: its name, its type, how many Cybelia modules are installed, the date of the last update. The working database always comes first, because it is the only one that pushes to production. Below the cards, your recent tickets and recent go-lives act as a memory.
Commenting is not enabled on this course.