Docs / Start here / The platform / Access control
Access control
Control who can read, change or share a resource. People and automated work have their own access.
Sharing and overlapping access
A grant gives an account, a team or the organization access to one resource. Direct and team grants combine with organization-wide sharing. The strongest applicable level wins. Removing one grant leaves access provided by another.
- View
- Read the resource and use the operations its View level allows.
- Edit
- Also change the resource. The operations differ by resource.
- Owner
- Also manage who has access. Several accounts or teams can hold Owner, and the last Owner grant cannot be removed.
Organization-wide sharing covers people. Service accounts need their own grant or membership of a team that has access. A service account can be a team Member, while a human Manager manages the team.
Workflows and jobs
- View
- Read the workflow, its jobs, execution logs and intermediate events. Run its existing jobs and test the workflow.
- Edit
- Also change jobs and workflow behavior, or delete the workflow. An editor can change what its configured actions do with data available to the run.
- Owner
- Also change the workflow’s access grants.
Jobs use the access of their containing workflow. Sharing a workflow also shares its logs and intermediate results, which can contain data copied from private inputs. The source integration keeps its own access grants.
Knowledge documents
- View
- Read the document and its saved branches and versions.
- Edit
- Also change its content and branches, or delete the document.
- Owner
- Also change the document’s access grants.
The document’s grants control access for workflow collaborators. Saving a job can give its managed account View on attached documents, as described under Job access.
Databases
- View
- Read the database’s schema and permitted rows, including SELECT queries.
- Edit
- Also insert, update and delete rows, subject to the database’s row rules.
- Owner
- Also change tables and schema, manage access and delete the database.
Database grants apply to the whole database. Row rules can further limit which records an account reaches. Requests made through an OAIZ app use the app’s own database grant rather than adding the signed-in person’s direct grants.
Apps
- Can use
- Sign in to the live app at its address and use it.
- Can change
- Also see drafts, change the app in Chat, publish, restore versions and rename it.
- Owner
- Also share the app and delete it.
Apps explains drafts, publishing and who can sign in.
Integration connections and tools
Every integration uses the same three roles. They apply the same way to a person in the application, their chat, the API and the CLI.
| Capability | View | Edit | Owner |
|---|---|---|---|
| Use permitted read tools | Yes | Yes | Yes |
| Use permitted write tools | No | Yes | Yes |
| Reconnect, reauthorize or change credentials | No | No | Yes |
| Configure, delete or manage the integration | No | No | Yes |
| Share or change access | No | No | Yes |
Read tools retrieve data. Write tools change data or perform an action in the connected service. A View or Edit grant can allow all tools, read tools only, or selected tools. Read tools only and a selected list do not include tools added later. A write needs Edit or Owner and the tool on the same grant, so a View grant cannot write even when its list includes a write tool. An Owner grant includes all tools and, on Slack, all channels.
Every role reads the connection’s events, including existing history. Read tools only limits calls, while the event data remains visible. Event access stays within the person’s grants and their channel limits.
On a Slack connection, a grant reaches all channels, selected channels, or the channels each person is in on Slack. A selected channel is set to View or Edit. Reading a channel’s messages or details needs View on that channel. Actions that change Slack, such as Send Message, Add Reaction, Upload File or Join Channel, need Edit on both the grant and the channel. A View channel gives read tools only, even under an Edit grant. Each grant is judged on its own, so two grants never add up to a tool or a write on a channel that neither allows.
When a grant does not reach all channels, a call must name the channel by its Slack ID, such as C0123ABCD. A channel name or a person’s user ID is refused. List Channels returns only the reached channels, and List Users, Get User Info, Get User Presence and Create Channel are unavailable. Event search, event details and counts show only events from those channels. The person sees only those channels and their members on the connection’s pages and in chat.
By default, a new Slack connection is shared with the organization at Edit with every tool. The person connecting can change this in the Access step. Each member reaches only the channels they are in on Slack, so they can read and post in their own channels without being able to manage the connection. Slack still applies its own posting rules to the OAIZ app. Joining or leaving a channel in Slack changes this access once OAIZ receives the event. This access applies only when the member’s verified OAIZ email address matches their Slack account’s email. A Slack account linked by hand gives none. Service accounts and job accounts never receive it. A job gets a fixed list of channels, as described under Job access. An Owner turns it off or on with Automatic access from Slack membership in the share dialog. Turning it on replaces any other organization-wide grant on the connection. Giving the organization other access turns it off.
These restrictions apply to tools called directly by a person or their chat. A job’s integration calls follow the grants of its job account instead. A call fails when no grant of that account allows the tool. Agent and Code jobs can also call only the integration tools selected in their configuration, so a Code job connection with no selected tools allows no calls.
Organization roles
An Administrator manages organization membership and settings. It also has Owner authority over workflows, knowledge documents, databases and apps in the organization. Integration connections still require their own applicable grants.
Member, Administrator and team Manager describe different roles. A team Manager manages that team. Resource Owner manages a resource’s audience. Neither label grants access to every other resource.
Accounts used for automated work
Each job runs as its own managed service account, including when a person starts a test or manual run. The initiating person’s permissions decide whether they can start it. The job account’s grants govern knowledge, database and integration tool access during execution.
A separately created service account also has its own resource grants and team memberships. Its manager can manage the account and its keys. That management role does not copy the manager’s resource permissions. A team can manage the account, and current Managers of that team manage it and its keys. Managing an account does not give it the team’s access. Adding it to the team is separate.
Job access
Saving a job can give its account access to the resources named in its configuration. Grants are limited by the saver’s access and the workflow owners’ access, up to Edit. Saving does not give broad tools access to other resources.
- Attached knowledge
- The account gets View on attached documents. A fixed Update knowledge target gets Edit when the required access is available.
- Database actions
- A query gives View on the database named in the action. A write gives access to that database at the available level, up to Edit.
- Integration tools
- An integration action, an Agent’s integration tools and a Code job’s selected tools give the account access to that connection, limited to those tools. The grant becomes Edit when a save adds its first tool, and stays View while it only lets the job start from the connection’s events. A read tool is added only when both the saver and the workflow owners can use it, and a write tool only when both hold Edit or Owner with that tool. On Slack, the account gets only the channels where both can use that tool, at the lower of their levels, so a tool that changes Slack is added only when that leaves Edit on at least one channel. When the owners lose a tool, the job account loses the access it received for that tool.
- Database tools
- Storage Query and Storage Execute work only on the databases chosen for each tool. The account gets View on the databases chosen for Storage Query and Edit on those chosen for Storage Execute.
- Broad document tools and dynamic targets
- Tools that choose documents at run time, and an Update knowledge target filled in from the event, need a person’s approval for additional access. The Give access preview lists the resources and levels to add. Confirmation adds that exact access. If the preview changes, review it and confirm again.
Access, in the job’s More actions menu, opens Manage access with Knowledge documents, Databases, Integrations and Events tabs. On Knowledge documents, add or remove documents and choose View or Edit. Events sets which events the job can read. Databases lists the databases the job’s configuration still needs, at the level the job uses. Change them in the job’s settings, not in this dialog. Give access saves the selection and requests the listed access. Documents in the selection follow the same save rules. Removing a document does not revoke access the job account already has. Removing an integration tool and using Give access revokes the access the job account received for that tool, and later saves of the job on that branch do not add it back. The job settings ask you to choose a database for Storage Query and Storage Execute before you save.
When a chat save needs additional access, its approval card shows the proposed resources and levels. Remove document rows or change their levels before Allow, or use Decline to give no access. Database rows stay at the level the job uses. The job stays saved. The result shows which access was given and whether any access remains to be reviewed.
Where to manage access
Use Share on a workflow, knowledge document, database or app to inspect and change its grants. A connection’s Access section has Share and tool restrictions. Only an Owner changes a resource’s grants. An Administrator has the same authority over workflows, knowledge documents, databases and apps, but not over connections.