Roles and Permissions
Roles in Lleverage define what actions a user can perform at both the Organisation level and the Project level. This system ensures secure, controlled access to workflows and settings while supporting collaboration across teams.
Organisation Roles
Owner (Organisation Admin)
Full control of the Organisation
Can manage all projects, workflows, members, and settings
Builder
Can create and edit workflows
Can run workflows
Ideal for workflow authors and maintainers
Operator
Can run workflows only
Cannot modify workflows or settings
Member
Can view everything in the Organisation
Cannot edit or run workflows
Project Roles
Project Admin (formerly Project Owner)
Controls limited to specific projects
Can manage workflows and prompts within the project
Can manage project-specific settings
Can add or remove users from the project
Can modify project connections and secrets
Project Member
Can view and use workflows within the project
Can contribute to workflows and prompts
Cannot modify project settings
Cannot add or remove users from the project
💡 This two-tier permission system allows for both broad Organisation management and granular Project-specific access control.
How to Manage Organisation Members
Click on your name/profile in the navigation panel.
Select Settings from the dropdown menu.
Navigate to the Members tab.
View all current Organisation members and their roles.
To change a member's role, use the role dropdown next to their name.
To remove a member, click the remove option.
To invite new members, click Invite Member.
⚠️ Only Organisation Admins can manage Organisation members. Members cannot invite or remove other users at the Organisation level.
How to Invite Members to Your Organisation
Go to Organisation Settings → Members.
Click Invite Member.
Enter the email address of the person you want to invite.
Select their role (Admin or Member).
Optionally, specify project access for the new member.
Send the invitation.
💡 Members can sign up using Google, Microsoft, or GitHub accounts, or through email with a magic link.
How to Set Up Automatic Domain Joining
Go to Organisation Settings → Members.
Look for the domain-based joining settings.
Enter your company email domain (e.g.
yourcompany.com
).Enable automatic joining for users with matching email domains.
Choose the default role for domain-matched users.
💡 This feature allows team members with your company email domain to join the Organisation automatically, streamlining the onboarding process.
How to Add Members to a Project
In Project Settings, open the Project Members tab.
Scroll to the Add Project Collaborators section.
View all Organisation members not yet added to the project.
Select the members you want to add.
Choose their role (Project Member or Project Admin).
Confirm to add them to the project.
⚠️ Users cannot access a workflow until they are added as members of the project, even if they have the workflow URL.
How to Share Workflows with Team Members
Ensure the user is added to your Organisation.
Add the user to the specific project containing the workflow.
Assign them the appropriate role (Member for view access, Admin for management access).
They can now access the workflow through the platform.
Alternatively, share the published workflow URL with them.
⚠️ Sharing a workflow URL will only work if the recipient is already a member of the project.
How to Manage Account Settings
Click on your name/profile in the navigation panel.
Select Settings from the dropdown menu.
Navigate through the available tabs:
Profile: Update your name, profile picture, and contact information
Login: Manage your email and SSO settings
Organisations: View and manage the Organisations you belong to
Projects: View all projects you have access to across Organisations
Make the desired changes and save your settings.
💡 Keeping your profile information up to date helps team members identify you in collaborative environments.
Best Practices for Permission Management
Follow the principle of least privilege: give users only the access they need.
Use Organisation Admin roles sparingly, reserving them for trusted team leaders.
Create project-specific roles for most team members to contain access.
Regularly audit Organisation and project memberships.
Remove access promptly when a team member changes roles or leaves.
Consider creating separate projects for different teams or departments.
Use automatic domain joining for large teams to streamline onboarding.
⚠️ Regularly review access permissions, especially for projects containing sensitive workflows or data, to maintain security and compliance.
Last updated