Object permissions
Understand how object permissions work in Retool, including access levels, universal and individual access, and folder inheritance.
The object permissions feature is not yet available on self-hosted instances. It's available to Enterprise or Business plan customers who have signed an annual agreement with a member of the Retool sales team. If you're on a self-service Business plan, contact the Retool sales team to learn more.
Object permissions control what groups and users can do with the objects (apps, resources, workflows, and agents) in your organization. You grant each group a permission level on individual objects, or on every object of a type, from the Object permissions tab on the group's detail page in Settings > Groups.
Object permissions are separate from organization roles. Organization roles control access to organization-wide settings, such as billing and SSO, and you manage them from the Roles page. Object permissions control what people can do with the things they build in Retool, and you manage them from the Groups page.
Permission levels
Every object permission is one of three levels: Use, Edit, or Own. Each level includes the abilities of the levels before it. For what each level lets users see and do for each object type, refer to Permission levels.
Universal and individual access
You can grant a group access in two ways.
- Universal access covers every object of a type in the organization, including objects created later. Use it for teams that need broad, ongoing access, such as a platform team that manages all resources.
- Individual access covers only the objects and folders you select. Use it for teams that work with their own set of objects, such as a marketing team that owns a few apps.
You set one universal permission level for each object type: apps, workflows, resources, and agents. A group can have universal access for one type and individual access for another. For example, a group can have Edit access to all resources and Use access to a specific set of apps.
When you set universal access for a type, it replaces the group's individual access to objects of that type. Before you save, Retool lists the individual assignments the change removes so you can review them.
The tradeoff is maintenance compared to control. Universal access needs no upkeep as your organization grows, but it grants access to everything of that type. Individual access stays narrow, but someone has to grant access each time a new object needs it.
For most organizations, start with individual access and expand to universal access only when a team genuinely needs access to everything. This follows the principle of least privilege and makes it easier to audit access.
Folder inheritance
When you grant access to a folder, the permission applies to all objects within that folder, including objects added later. If an object moves to a different folder, it inherits the permissions of its new parent folder.
Access an object inherits from a parent folder appears as inherited in the group's list. To change it, change the access on the parent folder.
How permissions combine
Permissions are additive. A user holds the combined permissions from every group they belong to, plus any object shared with them directly. When more than one source grants access to the same object, the user gets the highest level.
For example, if a group gives a user Use access to an app and a second group gives the same user Edit access, the user has Edit access.
To open a user's detail page, go to Settings > Users and select the user. The Object permissions tab lists each object the user can access and where that access comes from, such as a group or universal access. The tab is view only. To change a user's access, change it on a group the user belongs to.
Next steps
- Manage object permissions: Grant and review a group's access to objects.
- Permission levels reference: What Use, Edit, and Own permissions let users see and do.