Custom roles

custom roles let you create organization https //help make com/organizations and team https //help make com/teams roles with the permissions your users need instead of assigning only default roles, you can create a role, choose its permissions, and assign it to users in your organization or teams custom roles are available for enterprise plan users only for example, you can create a role that lets a user view and run scenarios without giving them access to billing, organization settings, or user management how custom roles work make uses organization roles https //help make com/organizations#organization roles and team roles https //help make com/teams#team roles to control what users can access and manage organization roles apply at the organization level team roles apply to a specific team this follows the existing two level permission model in make, where users belong to at least one organization and one team with custom roles, you can create your own role and choose permissions from a predefined list each permission controls a specific action, such as viewing organization details, managing users, or managing scenarios some permissions depend on other permissions when you enable or disable a permission, make may also enable or disable related permissions that the selected permission requires custom organization roles custom organization roles control what users can access and manage across the organization you can use custom organization roles to give users access to organization level permissions, such as organization details, organization members, billing information, feature controls, or organization settings custom team roles custom team roles control what users can access and manage in a specific team you can use custom team roles to give users access to team level permissions, such as viewing team data, managing scenarios, managing templates, or working with team resources team roles affect what users can do with data that belongs to a team team resources include scenarios, connections, webhooks, keys, data stores, data structures, templates, and other team owned assets permissions are all or nothing per resource type a permission like manage scenarios applies to every scenario in the team, not select ones to limit access to specific resources, use a separate team create a custom role to create a custom role for an organization or team custom roles can be created by org owners and admins only in the left sidebar, go to org > user roles select organization roles or team roles in the upper right corner, click + create role enter a name and description for the role enable the permissions you want to include in the role you can click enable all or disable all for each category of permissions click save role you’ve created a custom role and can assign it to users edit a custom role to find the custom role you created and edit the details in the left sidebar, go to org > user roles select organization roles or team roles find the custom role you want to update and click edit custom roles have a specific custom tag in the list update the custom role you can update the role's name, description, and permissions you can click enable all or disable all for each category of permissions go back to the user roles page by clicking the arrow next to the custom role's name click save role to save the changes you’ve updated the custom role and changed what assigned users can access or manage assign a custom role to assign a role in the left sidebar, go to org > org users click + invite user in the email field, enter the email address of the user in the name field, enter the name of the user from the role dropdown list, select the role to assign click save you have now assigned a role to a user to assign a role to an already existing user, click go to org users or team users table and update the existing role from the menu for more information see add users to an organization https //help make com/organizations#add users to an organization and manage team roles https //help make com/teams#manage team members manage linked permissions some permissions require other permissions to work correctly for example, a permission that lets a user manage organization settings may also require permission to view the organization when you enable a permission that requires other permissions, make shows a confirmation dialog you can enable the selected permission and its required permissions together when you disable a permission that other permissions depend on, make shows which related permissions will also be disabled review the list before you confirm the change duplicate a custom role you can duplicate a custom role from the role list in the user roles page, find the role you want to copy, click the three dots menu, and select duplicate role make opens the copied role in edit mode the copied role uses the original role’s permissions update the name, description, or permissions, then click save role the owner role can't be duplicated only one user can hold the owner role in an organization to transfer it to another user, use transfer ownership (three dot menu next to owner) to give it to another user delete a custom role you can delete a custom role from the role list in the user roles page, find the role you want to delete, click the three dots menu, and select delete role make asks you to confirm the deletion click delete to remove it this action cannot be undone