--- title: "Profiles and Permissions" url: https://docs.catalyst.zoho.com/en/getting-started/set-up-a-catalyst-project/profiles-and-permissions/ description: "Catalyst settings allow you to configure, personalize, and set up features that are relevant to your Catalyst project and your console, from adding collaborators for your project to managing payments and billing for your account." last_updated: 2026-09-28T11:04:26Z service: All Services type: general --- # Profiles and Permissions ### Introduction A profile represents a collection of permissions and privileges that gives project members access to various components and features inside a project. When you add a new project member, you must assign them to a specific profile for each project that they are added to. You can assign them to one of the default profiles, or define custom profiles based on your needs and use them instead. All profiles and permissions are project specific, and not account specific. You can assign the same individual to different profiles in different projects, and thereby grant different levels of access in each project. This enables you to provide only the relevant authorization to project members based on your organization's requirements. > **Note:** * Profiles do not apply to Catalyst account admins or the Super Admin. Only project members can be assigned to profiles for each project. * Catalyst provides permissions to project members in compliance with all relevant and applicable data protection laws and privacy guidelines, such as [GDPR](https://gdpr-info.eu/) and [HIPAA](https://www.hhs.gov/hipaa/index.html) regulations. This helps you readily implement user data protection regulations and build applications in accordance with them. ### Permissions The permissions defined by Catalyst are grouped into several categories. A Catalyst account admin can grant or deny any individual permission for a custom profile while creating it. Any default or custom profile can be assigned to a project member by an admin or another member with the _Add/Update/Remove Collaborators_ permission. Before you learn about the permissions defined in Catalyst, you must understand the **Access Types** available for those permissions: * **Editor** Editor access enables the project member to modify the configurations and data of the components they have permission to access. Editor access is available for all permissions defined in Catalyst. * **Viewer** Viewer access enables the project member to only view the configurations and data of the components they have permission to access. Viewer access is only available for four permissions from the permissions listed below: _Development Environment_, _Production Environment_, _Manage Settings and Configuration_. The details are explained in the table below. The following permissions are defined and available in Catalyst for the **Editor Access Type**:
| Permissions Group | Permissions | Description | |
|---|---|---|---|
| Manage Collaborators | Add/Update/Remove Collaborators | This provides permission to invite a project member or an admin, assign other projects to a project member, change the collaboration type for a lower level of hierarchy, or remove a project member from a project. | |
| Development Environment | Data Store Logs Signals Other Components | If Editor access to the Data Store, Signals, Logs, or Other Components is granted, the project member can configure the respective components and add data in them in the development environment of that project.
Note: Catalyst enables you to provide access to the Data Store, Signals, and Logs independently, and groups other components such as Circuits, Functions, Cron etc under "Other Components" because, the independent components can contain sensitive user data that you might require exclusive control on. This is done to adhere to all applicable data protection laws and privacy guidelines, such as GDPR and HIPAA. You will not be able to unselect the permission for "Other Components" in the development environment, because that is the minimum level of permission that can be granted to a project member. |
|
| Production Environment | Data Store Logs Signals Other Components | If Editor access to the Data Store, Logs, Signals, or Other Components is granted, the project member can configure the respective components and add data in them in the production environment of that project. Note: Similar to the development environment, Catalyst lists out the first three components independently as they can contain sensitive user data. If you select Data Store, Signals, or Logs in the production environment, "Other Components" will be selected by default. To unselect it, you will need to unselect any/all of the three independent components. |
|
| Manage Add-On Services | Enable/Disable Add-On Services | This provides the permission to enable or disable any of the Catalyst Add-On Services for that project. | |
| Manage Settings and Configurations | Perform Migrations | This provides the permission to migrate the project from development to production or production to development, and perform all migration actions. | |
| Enable/Disable Production Environment | This provides the permission to enable or disable the production environment any time after the project has been deployed to production. | ||
| Access Billing Components | If Editor access to this permission is granted, the project member can access the Billing settings (except the Overview and Manage Billing sections), create budgets, and view reports and breakdowns of that project. Viewer: If Viewer access to this permission is granted, the project member can only view reports and breakdowns of that project, but cannot create or manage budgets. Note: Only the admins of a Catalyst account can access the Overview section under the Billing settings because that section displays information from all projects of that Catalyst account. Only the admins of a Catalyst account can access the Manage Billing or Payments Portal section. This means that only admins can set up the payment method, add credit cards, and manage all payment and transaction related activities for the Catalyst account. A project member cannot perform these activities. |
||
| Add/Delete Mobile Packages | This provides the permission to add or delete Android or iOS SDK packages for the project from the Developer Tools settings in the console. | ||
| Access Audit Logs | This provides the permission to view the audit logs of all the projects in your Catalyst account. Note: If you choose to provide permission to access Audit Logs, you must provide permission to access Data Store, Signals, Logs, and Other Components prior to that. This is because, Catalyst shows the configurations and data of these components in the Audit Logs settings in the console, and therefore project members must already have permissions to those components. |