For administrators: who can use Nimbus, what it knows, what it connects to, and what it costs.
Access has two layers: whether Nimbus is enabled for a person at all, then what they're allowed to do with it. A role grants nothing while the person isn't enabled.
| Role | Can do |
|---|---|
| General | Use Nimbus |
| Trainee | Use Nimbus |
| Trainer | Use Nimbus, author trainings |
| Data analyst | Use Nimbus, query data directly |
| Admin | Everything below |
Admin covers: use, author trainings, query data, view the usage dashboard, administer Nimbus, manage knowledge sources, and create reports and files.
Granting one extra permission. Roles are starting points rather than fixed boundaries. A single capability can be added to one person without promoting them to a higher role, such as a trainee who also needs to query data.
The capabilities themselves: use Nimbus · author trainings · query data · view usage dashboard · administer Nimbus · manage knowledge sources · create reports and files · general assistant · web search · email access.
Each capability corresponds to an enforcement point in the software, so a permission cannot be granted for something the product does not already check.
Read only mode. An administrator can run Nimbus so it answers and reports but never writes. Reports still work, because saving a report isn't a change to your records.
Approvals, regardless of role. Creating or updating a record is summarised for confirmation first. Destructive actions always stop and ask.
What this is for. Teaching Nimbus a task once so anyone can be walked through it afterwards.
This is the highest value thing an administrator can do, and the one that makes on screen guidance work at all. A new workspace has nothing recorded, so nobody can be guided through anything until someone does this. Requires the author trainings capability.
How to record one. There is no menu to find. You ask Nimbus directly:
Let me teach you how to book a makeup session.
Recording starts in your own tab. Do the task normally, talking out loud as you go. Clicks, typing and navigation are captured, and your narration with them if you allow microphone access. On screen controls let you finish and save. Nimbus writes the narration up into step by step instructions, so you don't author a document.
Mark the parts that change. While recording, a field can be marked as varying, such as the customer, the date or the amount. On replay Nimbus asks for that value instead of reusing what you typed on the day. This is what makes a recording reusable rather than a one off macro. Passwords are never stored, in any recording.
What gets saved. The shape of the task, meaning which field, which button and which screen, and never the values you typed into it. That's why a recording is safe to share.
Keeping them working. Each step recognises its control by several signals rather than a fixed position, so a moved or renamed button gets found again. Every run records whether it finished and which step it stumbled on, so a recording that starts failing shows up as a health warning rather than a support ticket weeks later.
Turning a live task into a training. If someone asks Nimbus to do something and it works the task out on its own, that attempt can be saved as a reusable training in one action.