Read, or Read and write
For every app, each employee has one of three levels: None, Read, or Read and write. Reads run without asking; every write still asks you.
On this page
The three levels#
| Level | The employee can… |
|---|---|
| None | Not use the app at all. |
| Read | Use every one of the app’s reads, without asking. |
| Read and write | Also ask to write. Each write waits for your approval, unless a standing approval covers it. |
Access is per employee and per app. Peter in Finance might have Read and write in your accounting app and Read in Gmail, while Rui in Marketing has none of either.
Reads and writes, action by action#
Every app offers actions. A connection’s panel lists them under What this connection allows, each marked one of three ways:
| Marked | Means |
|---|---|
| Read | It only looks: search mail, read a file, list issues. Runs without asking for anyone with Read. |
| Write · asks you | It may change something: send an email, create an issue, update a deal, submit a form. Each one waits for you. |
| Not allowed | Royak can’t check what it would be sent, so no employee may use it. |
An action counts as a read only when the app says it just reads. Anything else is treated as a write, so a doubtful action always asks you.
What “writes wait for approval” means#
- 1
The employee prepares the write
The exact action, where it goes and every value it will send, such as the recipients and the message.
- 2
It waits in your Inbox
As a request under Needs you, with what it will change and why. See Approvals.
- 3
You decide
Approve it, and it is sent once, exactly as shown. Decline it with a reason, and the employee decides what to do next.
If the request changes after you approved it, you approve again. If the app doesn’t confirm whether a write happened, it is marked for you to check and is never sent twice.
Set access#
- On Connections, open the app and use Who can use it: Add an employee (they start at Read), change their level, or remove them.
- Or open the employee and select Edit: under What {name} can use, each connected app has None, Read or Read and write, applied at once.
The employee’s Works in list shows their access, such as “Slack · Read”, and marks an app whose access expired. Every change is recorded in Settings → Activity.
Rules that always hold#
- A department, job title, manager or skill grants nothing.
- New actions an app adds later start without access.
- Read and write never skips approval.
- A standing rule or a message never grants access; only you do.
Questions#
Is Read safe to give?
Read never changes anything in the app, but the employee sees what the app holds. Give it to employees whose work needs that information.
Can I let an employee write without asking each time?
Yes, for one action to one destination within caps, with a standing approval.
What happens to a task if I remove access?
The next call is checked again and refused, so the task can’t use the app any more.