Serverless360 lets organisations manage their Azure resources, those constitute their Line of Business. As an organisation you can add any number of your employees or extenal consultants as users to your Serverless360 account, to manage the associated resources. Employees using Serverless360 should be provided with exact permission they need. Too many permissions can expose an account to security violations. Insufficient permissions mean that your employees can’t get their work done efficiently. User access policy with custom role capability helps address this problem of offering fine-grained access management for Serverless360.
Serverless360 authenticates your organization users using your Azure Active Directory (AD). Users can be managed through the User Management feature under Settings module in Serverless360. New users can be assigned a role to define access control. The following table provides brief descriptions of the built-in roles:
|Administrator||As an account owner, you have full control over the application including access to licensing||Create and manage all resources, Invite Users to the account, Switch Account ownership to other Super User, Perform License Activation and Deactivation||-|
|Super User||Will have access to the whole application except licensing||Create and manage all resources, Invite Users to the account||Manage license|
Switch Account Ownership
Current Serverless360 Administrator can transfer the account ownership with one of the Super Users through the following steps:
- Login to Serverless360 as Administrator
- In the User Management section under Settings, find the option to Switch Ownership
- Choose from the available Super Users to switch ownership with.
Consider a business scenario, where the requirement is to provide Read-Only permission on a set of composite applications to a specific set of users. In this scenario, you can create a custom role definition along with the predefined roles.
- Click 'Add Role' in the User Management screen
- Enter a 'Role Name' and 'Role Description'
- Select the Composite Applications that should be accessible to this role
- Define Overall permission, applicable on the selected Composite Applications and its associated entities:
- Read Only- can view
- Manage - can manage
- Define permissions on 'Operations'
- Retrieve Message - Can view the message list and system properties
- Access Message Content - Can access message details like Custom Properties and Message body
- Process Message - Can perform message operations like defer, resubmit, repair & resubmit and delete the message
- Define permissions on 'Monitoring'
- 'View Alert History' -Can view the alert histories of the monitors already created
- 'Manage' - Can manage monitors
From Serverless360 2.0, a user can view associated entities in a Composite application to which the user is authorized to. Define the manage permission on Technology Stack, explicitly for Service Bus, Logic Apps, and Azure Functions to permit CRUD operations on the associated entities. Choosing,
- Manage - can perform CRUD operation on the associated entities
- Select View or Download option on Governance & Audit
Mapping Multiple Roles to User
Let us consider a shipping company which need to manage their Azure Serverless application built with Azure Serverless services. They have DevOps engineers who perform CRUD operations in the Azure entities and support engineer who has read only permissions to provide support to their customers.
Consider three Composite Applications in Serverless360
- Order Verification and processing,
- inventory management
- record keeping
and two roles
- DevOps Engineer
- Support Engineer
The role DevOps engineer has permissions to manage Azure entities in Composite Application ‘Order verification and processing ‘and ‘Inventory management ‘.
The role Support engineer has permissions to read data from Azure entities in Composite Application ‘Record keeping ‘and ‘Inventory management ‘.
Let’s consider 'Adam' who is a DevOps engineer but also performs support tasks at times. Here mapping multiple roles to user comes into picture where Adam will be a part of both the roles. Since Adam is a part of both the roles the permissions for the Composite Application and entities will be applied as follows
|Composite Application Name||Composite Application permission||Azure entities permission|
|Order verification and processing||Manage||Manage|
|Record keeping||Read only||Read only|
'Inventory management' is a Composite Application which has Manage permission in DevOps Engineer role and Read-only permission in Support engineer role. Since Adam is a part of both the roles the highest permission is applied on that composite Application.
Serverless360 custom role can be leveraged to:
Restrict users to hold:
- read-only or manage access to a selected Composite Applications (Logical group of Azure resources)
- read-only or manage access to a specified Technology stack (Service Bus, Logic App, Azure Function etc)
- permission only to Process Messages on entities associated within a Composite Application
- permission only to perform a specified action like View and Download Governance and Audit report
as the business scenario demands
Define custom permissions to a group of users