Understanding Ploy Permissions and Roles
This article explains the permission system in Ploy, helping administrators understand how to configure user access and roles effectively.
Written By Jacob Prime
Last updated 11 days ago
Overview
Ploy uses a granular permission system that allows you to control access to specific resources and actions. Each permission can be assigned independently, giving you fine-grained control over what users can see and do within the platform.
Note: Resource restrictions are currently in beta and may not apply to all areas of Ploy. Some features may bypass these restrictions.
Permission Types
Most resources support the following standard permissions:
read β View the resource and its data
write β Create, update, or delete the resource
Some resources have additional specialized permissions (such as run, grant, or execute_action) that control specific actions.
Resource Permissions Reference
Resource Restrictions
In addition to permissions, you can configure resource restrictions using Allow Lists and Block Lists:
Allow List: Specify which resources the user CAN access. Leave empty for no restrictions.
Block List: Specify which resources the user CANNOT access, even if they have the required permissions.
This is particularly useful if you have sensitive applications, groups or databases that you would like to be hidden from certain Ploy administrators.
Best Practices
Follow the principle of least privilege β only grant permissions that users need to perform their job functions.
Regularly review access permissions as part of your access review process.
Use Block Lists sparingly β they can make troubleshooting access issues more complex.
Document your permission strategy and ensure it aligns with your organization's security policies.
Need Help?
If you have questions about configuring permissions or need assistance with role management, please contact us.Β