Overview of AEM Assets Brand Portal
As a marketer, you sometimes need to collaborate with channel partners and internal business users to quickly create, manage, and deliver relevant digital content to customers. Timely delivery of relevant content across the entire customer journey is critical to driving greater demand, conversion, engagement, and customer loyalty.
However, it is a challenge to develop solutions that support efficient and secure sharing of approved brand logos, guidelines, campaign assets, or product shots with extended internal teams, partners, and resellers.
Adobe Experience Manager (AEM) Assets Brand Portal focuses on the marketer’s need to effectively collaborate with the globally distributed Brand Portal users by providing asset distribution and asset contribution capabilities.
Asset distribution allows you to easily acquire, control, and securely distribute approved creative assets to external parties and internal business users across devices. Whereas, Asset contribution enables the Brand Portal users with the ability to upload assets to Brand Portal and publish to AEM Assets, without needing access to the author environment. The contribution feature is called as Assets Sourcing in Brand Portal . And together, it improves the overall Brand Portal experience of asset distribution and contribution from the Brand Portal users (external agencies/teams), accelerates the time-to-market for assets, and reduces the risk of non-compliance and unauthorized access. See, Asset Sourcing in Brand Portal .
The browser-based portal environment enables you to easily upload, browse, search, preview, and export assets in approved formats.
Configure AEM Assets with Brand Portal
Adobe Experience Manager (AEM) Assets is configured with Brand Portal via Adobe Developer Console, which procures an IMS token for authorization of your Brand Portal tenant.
Configuring AEM Assets with Brand Portal via Adobe Developer Console is supported on AEM Assets as a Cloud Service, AEM Assets 6.3 and above.
Prerequisites to configure AEM Assets with Brand Portal
You require the following to configure AEM Assets with Brand Portal:
- An up and running AEM Assets instance.
- Brand Portal tenant URL.
- A user with system administrator privileges on the IMS organization of the Brand Portal tenant.
For more information, see configuring AEM Assets with Brand Poral .
User personas in Brand Portal
Brand Portal supports the following user roles:
- Guest user
The following table lists the tasks that users in these roles can perform:
Share a collection
Share assets as a link
Access to Admin Tools
* Guest users can browse, access, and search assets in public folders and collections only.
Any user having limited access to assets on Brand Portal without undergoing authentication is a guest user. The guest session allows users access to public folders and collections. As a guest user, you can browse through asset details and have full asset view of members of public folders and collections. You can search, download, and add public assets to Lightbox collection.
However, guest session restricts you from creating collections and saved searches, and share them further. Users in a guest session cannot access folder and collections settings, and cannot share assets as link. Here is a list of tasks that a guest user can perform:
A standard user in Brand Portal is typically a user with the role of Viewer. A user with this role can access permitted folders, collections, and assets. The user can also browse, preview, download, and export assets (original or specific renditions), configure account settings, and search for assets. Here is a list of tasks that a Viewer can perform:
A user with the role of Editor can perform all tasks that a Viewer can perform. In addition, and Editor can view the files and folders that an administrator shares. The user with the role of an Editor can also share content (files, folders, collections) with others.
Apart from the tasks that a Viewer can perform, an Editor can perform the following additional tasks:
An administrator includes a user marked as system administrator or Brand Portal product administrator in Admin Console. An administrator can add and remove system administrators and users, define presets, send email to users, and view portal usage and storage reports.
An administrator can perform all tasks that an Editor can perform the following additional tasks:
In addition to the above tasks, an Author in AEM Assets can perform the following tasks:
Alternate alias for Brand Portal url
Brand Portal 6.4.3 onwards, organizations can have one alternate (alias) URL for existing URL of their Brand Portal tenant. The alias URL can be created by having an alternate prefix in the URL. Note that only the prefix of the Brand Portal URL can be customized and not the entire URL. For example, an organization with existing domain geomettrix.brand-portal.adobe.com can get geomettrixinc.brand-portal.adobe.com created on request.
However, AEM Author instance can be configured only with the tenant id URL and not with tenant alias (alternate) URL.
To get an alias for tenant name in existing portal URL, organizations need to contact Adobe support with a new tenant alias creation request. This request is processed by first checking if the alias is available and then creating the alias.
To replace the old or delete the old alias, the same process needs to be followed.
Request access to Brand Portal
Users can request access to Brand Portal from the login screen. These requests are sent to Brand Portal administrators, who grant access to users through the Adobe Admin Console. After access is granted, users receive a notification email.
To request access, do the following:
- From the Brand Portal login page, select Click here corresponding to Need Access? . However, to enter the guest session, select the Click here corresponding to Guest Access? .The Request Access page opens.
- To request access to an organization’s Brand Portal, you must have a valid Adobe ID, Enterprise ID, or Federated ID.In the Request Access page, sign in using your ID (scenario 1) or create an Adobe ID (scenario 2):Scenario 1
You are redirected to the Request Access page. Scenario 2
- If you have an Adobe ID, Enterprise ID, or Federated ID, click Sign In . The Sign in page opens.
- Provide your Adobe ID credentials and click Sign in .
You are redirected to the Request Access page.
- If you do not have an Adobe ID, to create one, click Get an Adobe ID from the Request Access page. The Sign in page opens.
- Click Get an Adobe ID . The Sign up page opens.
- Enter your first and last name, email ID, and password.
- Select Sign up .
- The next page displays your name and email ID used to request access. Leave a comment for the administrator, and click Submit .
Product administrators grant access
Brand Portal product administrators receive access requests in their Brand Portal notification area and through emails in their inbox.
To grant access, product administrators need to click the relevant notification in Brand Portal notification area and then click Grant Access . Alternatively, product administrators can follow the link provided in the access request email to visit Adobe Admin Console and add the user to the relevant product configuration.
You are redirected to the Adobe Admin Console home page. Use Adobe Admin Console to create users and assign them to product profiles (formerly known as product configurations), which show as groups in Brand Portal. For more information about adding users in Admin Console, see Add a user (follow Steps 4-7 in the procedure to add a user).
Brand Portal languages
You can change Brand Portal language from Adobe Experience Cloud Settings.
To change the language:
- Select User > Edit Profile from the top menu.
- On Experience Cloud Settings page, select a language from the Language drop-down menu.
Brand Portal maintenance notification
Before Brand Portal is scheduled to go down for maintenance, a notification is displayed as a banner after you log in to Brand Portal. A sample notification:
You can dismiss this notification and continue using Brand Portal. This notification appears in every new session.