Admins and Managers can now define exactly which workflow elements Builders are allowed to use. These access controls help enforce governance, protect sensitive data, and simplify the building experience.
Capabilities
With Workflow Access Controls, Admins can now restrict access to:
- Workflow step types (e.g., Sign, Conditional Logic)
- Integrations (e.g., Salesforce, Epic, Slack)
- Sign field types (e.g., Date Signed, Signature, Title)
These restrictions can be applied at both the account and project levels. Builders will only be able to use the items explicitly made available to them.
Who Can Use It
- Admins can manage access settings for all projects across the account.
- Managers can override Admin settings at the individual project level.
- Builders are limited to using only the allowed elements. Restricted items appear with a lock icon.
- Admins and Managers retain full access to all steps, integrations, and Sign fields, even those restricted to Builders.
How It Works
1. Set Defaults at the Account Level
From the Projects page, Admins can open the Access Control Settings Panel to set default restrictions for all projects.
- Toggle access to specific step types, integrations, or sign fields.
These defaults will apply to all new projects unless manually overridden.
2. Override Settings on a Per-Project Basis
From within a project, Admins and Managers can override the global settings:
- Enable or disable specific steps, integrations, or sign fields for just that project.
Note: This is useful for testing or for projects with unique needs.
3. Builder Experience
When Builders try to use a restricted item:
- It will appear in the UI with a lock icon or greyed out.
- They won’t be able to add or edit the restricted item unless it was already added by an Admin or Manager before the restriction was applied.
Note: Newly released Intellistack workflow steps, integrations, and Sign fields are available by default and must be disabled by Admins or Managers if not desired.
What’s Not Included
- These controls do not currently apply to form fields in the Form Builder.
- Workflow steps added before a restriction is applied will remain in place but can’t be edited by Builders.
For more granular control or project-specific needs, repeat this process from within any project.
Comments
0 comments
Article is closed for comments.