Permissions Management

If you need to assign different permissions to employees in your enterprise to access the purchased KooPhone resources on Huawei Cloud, Identity and Access Management (IAM) is a good choice for fine-grained permissions management. IAM provides identity authentication, permissions management, and access control, helping you secure access to your Huawei Cloud resources. If your Huawei Cloud account does not require individual IAM users for permissions management, you can skip this section. This permission setting applies only to the KooPhone service, but not to the KooPhone client.

Huawei Cloud IAM is a free service. You only pay for the resources in your account.

With IAM, you can control access to specific Huawei Cloud resources. For example, if you want some software developers in your enterprise to use KooPhone resources but do not want them to delete KooPhone resources or perform any other high-risk operations, you can create IAM users and grant permissions to use KooPhone resources but not permissions to delete them.

IAM supports role/policy-based authorization and identity policy-based authorization.

The following table describes the differences between these two authorization models.

**Table 1** Differences between role/policy-based authorization and identity policy-based authorization
Authorization Model	Core Relationship	Permissions	Authorization Method	Scenario
Role/Policy	User-permission-authorization scope	System-defined roles System-defined policies Custom policies	Assigning roles or policies to principals	To authorize a user, you need to add it to a user group first and then specify the scope of authorization. It provides a limited number of condition keys and cannot meet the requirements of fine-grained permissions control. This method is suitable for small- and medium-sized enterprises.
Identity policy	User-policy	System-defined identity policies Custom identity policies	Assigning identity policies to principals Attaching identity policies to principals	You can authorize a user by attaching an identity policy to it. User-specific authorization and a variety of key conditions allow for more fine-grained permissions control. However, this model can be hard to set up. It requires a certain amount of expertise and is suitable for medium- and large-sized enterprises.

Policies/identity policies and actions in the two authorization models are not interoperable. You are advised to use the identity policy-based authorization model. For details about system-defined permissions, see Role/Policy-based Permissions Management and Identity Policy-based Permissions Management.

For more information about IAM, see IAM Service Overview.

Role/Policy-based Permissions Management

KooPhone supports role- and policy-based authorization. By default, new IAM users do not have permissions assigned. You need to add a user to one or more groups, and attach permissions policies or roles to these groups. Users inherit permissions from their groups to grant specific operation permissions on cloud services.

KooPhone is a project-level service deployed and accessed in specific physical regions. When you set Scope to Region-specific projects and select the specified projects (for example, ap-southeast-2) in the specified regions (for example, AP-Bangkok), the users only have permissions for resources in the selected projects. If you set Scope to All resources, the users have permissions for resources in all region-specific projects. When accessing KooPhone, users need to switch to the authorized region.

Table 2 lists all the system roles supported by KooPhone. This permission setting applies only to the KooPhone service, but not to the KooPhone client.

**Table 2** KooPhone system permissions
Role/Policy Name	Description	Type	Role Content
KooPhone Administrator	Role that has all KooPhone operation rights. Users with the permissions can have all rights supported by KooPhone.	System-defined role	Content of the KooPhone Administrator Role
KooPhone ReadOnlyUser	User who has the read-only permissions on KooPhone.	System-defined role	Content of the KooPhone ReadOnlyUser Role

Table 3 lists the common operations supported by system-defined permissions for KooPhone. Choose proper permissions according to this table.

**Table 3** Common operations supported by system-defined permissions for KooPhone
Operation	KooPhone Administrator	KooPhone ReadOnlyUser
Purchase UNI Cloud Terminal	√	×
View organizations and users details	√	√
Create an organization	√	×
Add a department	√	×
Add a member	√	×
Query an instance (name and specifications)	√	√
Set parameters in the instance list	√	×
Restart an instance	√	×
Power on an instance	√	×
Power off an instance	√	×
Renew an instance	√	×
Unsubscribe from an instance	√	×
Uninstall an app	√	×
Delete an instance	√	×
Bind/Unbind a user	√	×
Query details about a deployment	√	√
Upload an app	√	×
Uninstall an app	√	×
Install an app	√	×
Query security control details	√	√
Enable anti-screen capture	√	×
Disable anti-screen capture	√	×
Enable video watermark	√	×
Disable video watermark	√	×
Delete app blacklists/whitelists in batches	√	×
Create an app blacklist/whitelist	√	×
Enable the app blacklist/whitelist	√	×
Disable the app blacklist/whitelist	√	×
Modify an app blacklist/whitelist	√	×
Delete an app blacklist/whitelist	√	×
Enable encrypted transmission	√	×
Disable encrypted transmission	√	×
Query CORS rules	√	√
Add/Edit/Delete CORS rules	√	×
View callback events	√	√
Add/Edit/Delete callback events	√	×

Identity Policy-based Permissions Management

KooPhone supports identity policy-based authorization. Table 4 lists all the system-defined identity policies for KooPhone. System-defined policies in identity policy-based authorization are not interoperable with those in role/policy-based authorization.

**Table 4** System-defined identity policies for KooPhone
Identity Policy Name	Description	Type
koophoneFullAccessPolicy	Full permissions for KooPhone	System-defined identity policy
koophoneReadOnlyPolicy	Read-only permissions for KooPhone	System-defined identity policy

Table 5 lists the common operations supported by system-defined identity policies for KooPhone. Choose proper system-defined identity policies according to this table.

**Table 5** Common operations supported by system-defined identity policies
Operation	koophoneFullAccessPolicy	koophoneReadOnlyPolicy
Read-only permissions for KooPhone	√	√
Creation permissions for KooPhone	√	x

References

IAM Service Overview.
For details about how to create a user group or user and grant KooPhone permissions, see "Creating a User and Granting KooPhone Permissions" in User Guide.

Content of the KooPhone Administrator Role

{ 
        "Version": "1.1",
        "Statement": [ { 
            "Effect": "Allow",
             "Action": [ 
                 "Koophone:*:*" 
             ] 
         }] 
      }
   }
}

Content of the KooPhone ReadOnlyUser Role

{ 
        "Version": "1.1",
        "Statement": [ 
            {  
                 "Action": [ 
                     "koophone:*:query*",
                     "Koophone:*get*",
                     "Koophone:*list*"
                 ], 
                 "Effect": "Allow",
             } 
          ] 
       }
    }
}

Previous topic: Principles

Next topic: Constraints