Permissions
Permissions decide what you can do in the Rule Repository. Your application gives every user a set of permissions, usually according to their role: a business analyst may write rules and tests, an approver may also make versions live, and an administrator may delete. The repository then shows you everything you may see, turns off what you may not do, and refuses on the server anything you are not allowed to do, so the rules of your organization hold whatever screen or tool is used.
Permissions are set by your application, not in the repository's screens. If you need a permission you do not have, ask whoever manages your application's users.
What Everyone Can Do
Every user of the repository can:
- see the Source Objects, Source Versions, Rules and Rule Versions grids and open their dialogs;
- browse a source version's fields, compare versions, and copy a rule or a definition with the copy icons.
What Needs a Permission to See
These areas each have a permission to view them. Without it, the area is hidden completely, together with every way into it: its tab at the top of the screen, its icons and count columns in the grids, its bars on the Stats tabs and its entries in Show related....
- Drafts: the Drafts grid and draft dialogs.
- Tests: the Tests grid, saved tests, and value templates.
- Live Evaluations: the evaluations your application recorded, and their charts.
- User Activity: the activity log. Even with it, you do not see entries about drafts, tests or evaluations you may not view.
- Internal Notes: the Internal Notes tab of every dialog.
What Needs a Permission to Do
Each action has its own permission. In short:
| Object |
Actions with their own permission |
| Source objects |
Changing the name and description; deleting |
| Source versions |
Changing the name and description; making live; taking offline; deleting |
| Rules |
Creating; changing the name and description; deleting |
| Rule versions |
Creating; changing the name and description; making live (and saving with Save & Go Live); taking offline; requesting approval; approving and declining; deleting |
| Drafts |
Creating; changing; turning into a version; deleting |
| Tests |
Running; saving a new test; changing a saved test; deleting; running in batches; running tests that call your application's real methods |
| Value templates |
Creating; changing; deleting |
| Live evaluations |
Saving an evaluation as a test |
| Notes |
Adding; deleting any note |
| AI |
Using the AI Assistant; using the AI Rule Editor; reading every user's AI conversations and the usage figures |
Some permissions come with others. For example, approving a version also needs permission to make versions live, and someone who may make versions live never needs to request approval: they save with Save & Go Live or Save Version instead.
What You See Without a Permission
- A button you may not use is shown but turned off. Hover over it to see why; usually, "You do not have permission to do this."
- An area you may not see is not shown at all, as described above.
- If your permissions change while you work, the repository applies the new ones as soon as it next hears from your application, and tells you if something you just tried was refused.
What AI Agents and Services May Never Do
Some limits apply to every AI agent and automated service, whatever permissions they are given, including when an AI acts for you:
- they never make a version live or take it offline;
- they never approve or decline a request for approval;
- they never delete anything;
- everything they save is saved as a request for approval, for a person to review.
These limits also apply to the AI Assistant, which works with your permissions and within these limits.