Permissions

Each product offers specific permission granularity, which allows you to have appropriate control, limiting user actions and privileges when necessary.

Access management is different in Sensedia Platform 4.x versions. Check the documentation.

On this page, see more about permissions for:

Concepts

  • Resource: any entity in a product that can be protected, such as files, APIs, data, or features.

  • Permission: determines whether a specific action can be performed on a given resource, such as create, delete, list, update, view, etc.

  • Role: a set of permissions grouped based on specific functions (e.g., "Administrator," "Editor," "Reader").

Permissions are assigned to roles, and users inherit these permissions by being associated with the roles.

Practical example

I want some users to only be able to view the Data Streamings already configured in Sensedia Analytics, while others can, in addition to viewing, also create, edit, and delete Data Streamings.

  1. Create two roles: "Data Streaming Viewer" and "Data Streaming Editor".

    • Creating the "Data Streaming Viewer" role:

      • On your Sensedia Platform home screen, click Roles in the menu located on the right side. home screen with an indication for the roles menu
        This screen may vary depending on the Sensedia solutions you have.

      • Click the + Create Role button, located in the top right corner of the screen, to create a new role.
        roles screen with the create role button.

      • In Role information, fill in the name (do not use spaces) and, optionally, the role’s description. Click Continue.
        part of the overview screen with the role name filled in.

      • In Assign Permissions, search for "Analytics" and select only the "Data Streaming View" permission in "Data Streaming", then click NEXT.
        permissions screen with the Data Streaming View permission selected.

      • In Review, review the role’s information and click Create Role.

    • Creating the "Data Streaming Editor" role:

      • Repeat the same steps listed above to create the "Data Streaming Editor" role, but this time select the permissions:

        • "Data Streaming View",

        • "Data Streaming Create",

        • "Data Streaming Update", and

        • "Data Streaming Delete" in "Data Streaming"
          part of the permissions screen with the Data Streaming View, create, update, and delete permissions selected.

  2. Associate the users with the created roles.

    • In Roles, locate one of the created roles and click > in the Actions column.
      roles screen with the actions button.

    • Click the Users tab and then click the Assign User button.
      users tab with the assign user button.

    • Select the desired users and click + Add 'n' Roles ('n' is the number of selected users).
      permissions assign user add.

    • Click Assign Roles to complete.

    • Repeat the same process for the other role created.

Users who were associated with the "Data Streaming Viewer" role will only be able to view existing Data Streamings, while users who were associated with the "Data Streaming Editor" role will be able to create, edit, and delete Data Streamings.

Adaptive Governance and Developer Portal

  • Make sure the user is associated with a role that has the necessary permissions to access the Adaptive Governance and/or Developer Portal feature.

  • In addition to permissions for Adaptive Governance and/or the Developer Portal, you may also need to configure some permissions that are related to other products or features.

To access all features related to the API catalog, for both Adaptive Governance and the Developer Portal, select the permissions for Connect Catalog, as well as the permissions for the product itself.

permissions screen with the Connect Catalog permission selected

API Management (Sensedia Platform)

In addition to permissions for the API Management (Sensedia Platform) features, you may also need to configure some permissions that are related to other features.

For example, to view a list of APIs in API Management (Sensedia Platform), the user must be associated with a role that has the permissions:

  • "API List" in "API Platform" and

  • "Groups" in "Access Control".

See more details about the necessary permissions for each feature in the API Management user guide.

Thanks for your feedback!
EDIT

Share your suggestions with us!
Click here and then [+ Submit idea]