Powered by Zoomin Software. For more details please contactZoomin

Progress Data Platform Help

Share access

  • Last Updated: November 19, 2026
  • 2 minute read
    • Documentation

After Progress Data Platform authenticates a user or an application, it uses roles to determine what that identity can do. Roles are assigned at the account, platform feature, project, and data source levels. For information about how users and applications authenticate, see Authentication.

Roles

The following table describes the levels at which roles are assigned:

Level Roles What the roles control
Account Owner or Member Owners can invite users to the account, remove users from it, and manage API keys.
Platform features Platform roles Access to Data Platform features. See Manage platform access for more information.
Project Reader or Writer Reader can view project data. Writer can view and update project data.
Data source Reader or Writer Reader can view the data source. Writer can view the data source and manage who has access to it.

Roles apply to both users and API keys. For example, an API key must have a project role before it can work with the data in that project. See Grant an API key access to a project.

How access is enforced

Data Platform checks access both when a user or application requests an action and when it reads or writes data. A user who does not have access to a project, for example, cannot retrieve its data through any of the following:

  • The Data Platform interface
  • The API
  • An agent
  • A Model Context Protocol (MCP) client

Account membership and project access are separate. Users must belong to the account before you can add them to a project, and joining an account does not grant access to any of its projects.

Note: Every project must have at least one human user with Writer access.

Manage access

Use the following topics to manage user and API key access:

Access control recommendations

Follow these recommendations to limit access to your data:

  • Grant the least access needed.

    Assign Reader rather than Writer when a user or API key does not need to update data, and grant project access only to the projects that it needs. Assign the Platform Manager and Data Source Admin roles only to users who need them.

  • Review access regularly.

    Remove users from projects and from the account when they no longer need access, and remove API keys from projects that no longer use them.

  • Limit the tools that custom agents can use.

    Select only the tools that an agent needs, especially tools that can change data or run pipelines.

Alert