Permit.io StrawberryHand the Permit.io roles to a companion
A companion works the 4 operations your Permit.io account exposes. It can remove a role and create a tenant, and every one of those waits on an approval card showing the role before it changes.
Open the role. Check it against something else. Write the change. Move to the next one. That is the Permit.io afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing landing on a role until you approve it.
What it can do is exactly what Permit.io exposes to an account you authorise and nothing beyond it: 4 operations, no reads and 4 writes. In practice that means it can remove a role, create a tenant and create a relationship tuple, and work across the roles, relationship tuples and tenants.
The Permit.io API stops at Permit.io. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the roles or ask you for them?
In the tab.
Permit.io exposes no read operation to a connected account, so a companion opens Permit.io in the session you are already signed into and reads the screens you would.
The roles are what most of this inventory is about, alongside the relationship tuples. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Permit.io admin becomes a queue you review.
What happens before it can remove role?
All 4 write operations wait for you.
A companion can remove a role, create a tenant and create a relationship tuple, and each one is staged on an approval card first: you see the role, the field and the new value before it lands in Permit.io.
Nothing in Permit.io is sent, changed or deleted on your behalf without that click, and a rejected card leaves the role exactly as it was. The gate is the same one on every surface, described at security.
- Remove Role
- Create Tenant
- Create Relationship Tuple
- Assign Role
Does the role sweep have to be asked for every time?
Yes.
Saved as a routine, the Permit.io roles pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the engineering admin, the Permit.io roles sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents