Who can do what
Four permissions control the Ontology platform. Holding any one of them opens Organization → Modules → Ontology platform. Each change needs its own.
| Permission | Lets someone |
|---|---|
| See the ontology | See types, links, actions, runs and usage. Changes nothing. |
| Manage types and links | Add types from connected apps, files and CSV files, upload documents and newer CSV files, delete types you’ve added, add properties, write what types, properties and values mean, and add, change and delete links. Never changes Flowstate’s own properties. |
| Manage actions | Add, change and delete actions, including agents and code that run on your data, set what each may read and change and its limits, switch them on and off and try them. |
| Respond to runs | Answer a run’s question, run a failed run again, or skip it. |
Changing Work, people or teams asks for one more permission, the same one the rest of Flowstate asks for when you change their fields:
- Adding a property to Work, people or teams also needs Create Entity Configuration.
- Saving an action that’s allowed to create, change or delete Work, people or teams also needs Update Entity Configuration. So does the ready-made setup that links an app’s records to Work.
Administrator and Config Admin hold all four, and both of these. No other built-in role holds any of them.
Give someone access
To let someone build on the Ontology platform without making them an administrator, such as a solution architect, give their role the permissions they need.
- Go to Organization → People & roles → Roles.
- Create a role or open an existing one. See Invite people and manage their access.
- Under Ontology platform, tick the permissions.
- Save the role.
Some useful sets:
| For | Permissions |
|---|---|
| Someone who builds and runs it | All four |
| Someone who sets up data but not actions | See the ontology, Manage types and links |
| Someone who answers runs’ questions | See the ontology, Respond to runs |
| Someone who only watches | See the ontology |
Connecting an app also needs access to integrations. See Roles and permissions.
What only Flowstate does
Whatever a role holds, Flowstate sets these with you:
- switching the Ontology platform on for your organization
- raising your organization’s monthly limits for AI spend and compute, and how many runs run at once
Nobody can change Flowstate’s own properties, such as a person’s name, through the Ontology platform.
Who changed what
Changes people make on the Ontology platform are recorded in your organization’s activity log. See Activity log. What actions change shows in each type’s History, naming the run.