Profiles and permissions
A profile defines what a person can do in Proton: each profile is a set of permissions, such as viewing automations, running in the Automation Center or inviting users. Each person has one profile in each organization. Profiles are in Access & Teams > Profile.
What a person sees also depends on teams, through the team rule. See Teams.
Default profiles
The default profiles come ready-made and can't be changed: in the list, they have the Default badge and only open in View mode.
| Profile | For whom |
|---|---|
| Owner | Superuser, with full access. Not assigned through the portal. |
| Admin | Administrator, with access to everything. It's the only profile that sees automations from every team, and only an Admin can give the Admin profile to someone else. |
| Manager | Manager or coordinator: automations, resources, users and teams, integrations and repositories, and runs in the Automation Center. Can't schedule, create recurring runs, or change profiles, runners or licenses. |
| Analyst | Analyst: automations and resources, and runs. Reads users, teams and profiles. Can't schedule or create recurring runs. |
| Executor | Runs automations and views the results. It's the profile of robot accounts. |
| Reader | Read-only: dashboards and results. |
| Billing Manager | Finance: licenses and costs, plus read access to users and teams. |
| Robot Operator | Robot operator: monitors runs, runs and stops them in the Automation Center and handles operation exceptions. Doesn't change records. Home opens in the Operation lens. |
Create a profile
Add opens Create Profile:
- Enter the Profile Name and, if you want, the Description (up to 500 characters).
- Check the permissions. The shortcuts help: Read Only, Full CRUD, Clear All and Copy from... (which starts from another profile).
- Save.
Profiles you create show up with the Custom badge and can be edited and deleted. When you delete a profile in use, the people who have it need another profile.
The permissions
Permissions are organized in tabs, one per area. In each tab, the rows are the entities and the columns are the actions: read (view), create, update (edit), delete and the specific actions of some entities. Select all checks the whole tab.
| Tab | Entities |
|---|---|
| Configuration | System, Params de Config (the configuration parameters), Integration (the integrations) and Git Repository. |
| Automation | Automation Group, Cycle, Automation Center, Automation, Dataset, Dataset Variable, Dataset Component, Dataset Parameter, Component, Parameter, General Parameter, Results, Tags, DatasetRun (the run), Validation (the run validation), GeneralParameterCategory (the general parameter categories), Environments, Jira requirements and Jira bugs. |
| Resources | Files and Data Tables. |
| bdd | Feature (the Gherkin files of repositories with BDD). |
| mobile | Mobile App. |
| Identity | Username, Team and Profile. |
| Infrastructure | Runner, Cluster and Cloud Runner. |
| Billing | License (the licenses) and CostManager (the costs). |
| Processes | Business areas, People and Process map. |
| Operation | Operation exceptions. |
Specific actions
| Entity | Action | What it allows |
|---|---|---|
| Automation Center | run | Run now. |
| Automation Center | schedule | Schedule a run. |
| Automation Center | recurring | Create and change recurring runs. |
| Automation Center | addAutomation and removeAutomation | Add datasets to and remove them from groups. |
| Automation | private | Mark the automation as private and choose its teams. |
| Automation | exclusiveAgent | Select Agents: the runners and clusters reserved for the automation. |
| Dataset | duplicate and transfer | Duplicate and transfer datasets. |
| Files | download | Download files. |
| Username | changePassword | Change another person's password and manage robot account tokens. |
| Username | changeTeams | Add the person to and remove them from teams. |
| Operation exceptions | assign | Assign the exception to another person. |
| Feature | moveBranch | Move Gherkin files between branches. |
:::tip No access The menu shows every item to everyone. Without the view permission, the screen tells you that you don't have access; without the permission to act, the button is disabled. If you're missing a permission, talk to whoever manages Proton at your company. :::
Running scheduled and recurring runs also depends on the plan. See Licenses.
Permissions and mobile
Viewing, creating, editing and deleting profiles are permissions of the Profile entity, in the Identity tab. The screen is designed for desktop.