某些 Creative Cloud 应用程序、服务和功能在中国不可用。
Vaatate praegu abisisu järgmise versiooni jaoks::
As a Brand Portal administrator, you can perform several administrative tasks, including managing users and groups. However, to be able to use groups, you must first define them using Admin Console. You can subsequently assign roles to these groups in Brand Portal.
After logging in as an administrator, you can use Admin Console (Enterprise Dashboard) to add users to Brand Portal. You can also create product configurations after navigating to the Brand Portal product. Product configurations are synced as groups in Brand Portal. Later, you can use them to assign group privileges to users in Brand Portal.
You can add any user that is a member of Adobe Marketing Cloud to Brand Portal. If you are a product administrator, you can define multiple product configurations and categorize users by adding them to product configurations. Product configurations are synced to Brand Portal as user groups. You can leverage the user groups to manage user roles and share folders and asset URLs from within Brand Portal.
-
To provide administrator rights to the user, choose Admin Rights, and then select the particular role from the list.
Märkus.
Configuration Admin is not an administrator in Brand Portal. Avoid using Configuration Admin if you want to assign administrative rights to a user.
Märkus.
Adobe recommends that you avoid using the System Administrator role, because this role has the entire set of privileges for an organization, irrespective of the product. For example, a system administrator of an organization that includes three marketing cloud products has the entire set of privileges for all the products.
In contrast, the Product Admin role has administrator privileges for a specific product only. If you want to enforce a more granular access control within Brand Portal, use the Product Admin role instead of System Administrator.
However, using the System Administrator role does not disrupt any Brand Portal functionality.
Product configurations provide a mechanism to categorize users. For example, if you want to share a particular asset folder with a set of users, you can create a product configuration to include these users. Admin Console includes a default product configuration for Brand Portal to which you can assign users. However, you can create custom product configuration groups.
Product configuration group maps to user groups within Brand Portal. You can add users to product configuration groups and use these groups in Brand Portal for bulk operations, such as sharing a folder with large number of users.
Brand Portal periodically fetches the product configurations that you create using Admin Console, and copies them as user groups within the Brand Portal product. You can share content (assets/collections) to group members through the Settings tab or URLs.
An administrator can modify roles for users in Brand Portal. An admininistrator may also assign a role to a group to simultaneously change the roles of the associated members.
To revoke administrator privileges for a user use Admin Console only. Launch Admin Console, open the user profile, and then remove the System Adminstrator/Product Administrator privileges for the user.
In adition to the Administrator role, Brand Portal supports following roles:
- Viewer: A user with this role has limited privileges. The user can view the files and folders that an administrator shares with the user. The user can also search and download assets. However, the user cannot share content (files, folders, collections) with others.
- Editor: A user with this role has all the privileges of a Viewer. In addition, Editor can share content (folders, collections, links) with others.
-
In the Users tab, select a user for which you want to modify the role. You can also select multiple users.
Märkus.
Notice that the Role list for Administrator users are disabled. You cannot select these users to modify their roles.
Märkus.
The user role is also disabled if the user is a member of the Editor group. To revoke editing privileges from the user, either remove the user from the Editor group or change the role of the entire group to Viewer.
