FinOps: The Future of FinOps is CloudOps Learn why

Feature Friday Automation & Orchestration Continuous Compliance

Feature Friday: Creating a New Role with Project Permissions

David Haller

2 min read

Managing user permissions can be a complex task, especially in applications with diverse functionalities. In this Feature Friday video, we’re sharing the process of creating project-specific roles to allow you to grant precise access to users based on their roles and project requirements.

Create a New Role

To get started, the first step is to create a new role tailored to your project's needs.

  1. Go to Settings and select Permissions.
  2. Select Role to create a new role.
  3. Enter the name of the new role. In our example, we'll name the role "Project Compliance Member."
  4. Click on Create Role.

Add Permissions to the Role

Now that you've created the role, it's time to define its permissions. Here's how:

  1. From Permissions, select Permission Schemes.
  2. Select the Default Project Permission Schemes, as you want this role to be project-specific.
  3. Search for the permissions you want to apply to this role. In this case, we're looking for "Browse Project Compliance."
  4. Select the "Project Compliance Member" role and update the permission scheme.

Apply the Role to a Project

With the permissions set for the role, the next step is to apply it to a specific project. Follow these steps:

  1. Navigate to Projects, and select the project where you want to assign this role. In the example, it's the "Asthma Research Production Project."
  2. Click on the three dots at the top right corner of the project to access the Manage User Permissions option.
  3. Locate the "Project Compliance Member" role in the list and add the user to this role on this project.
  4. Save the changes to apply the permissions to the user for this project.

Test the Role

To ensure that the role and permissions work as intended, log out as the admin user and log back in as the user who received the new role. Here's what to expect:

  1. Upon logging in, you'll notice that the main screen doesn't display any compliance or financial data - apart from the project this user has access to.
  2. Navigate to your "Asthma Research Production Project." You'll see that with the permissions assigned through this project-specific role, the user doesn't have access to billing data or cloud management information.
  3. However, if you access the compliance section, you'll find that the user has full access to view the compliance information.

By creating project-specific roles and meticulously defining their permissions, you can ensure that users have access only to the areas of the application relevant to their roles and responsibilities. This approach enhances security and streamlines access control, allowing for efficient management of your application's resources.

About the Author

David Haller

David is a Technical Account Manager at Kion.

Start your cloud operations journey.

Request a demo today,