# Acquia DAM Certification

Our sandbox Acquia DAM environment can be found here: <https://tpximpact.widencollective.com/>

Request a login on #dx\_tech channel in Slack

Once you are in, head over to The Widen University and run through their training courses from top to bottom: <https://university.widen.com/>.&#x20;

Take them at the pace you want and make notes as you head through.  A couple of hours a week is probably enough.

There's also a [Drupal site setup here](https://dev-tpxdam.pantheonsite.io/) that you can use to see how the Drupal integration works.  Ask in #dx\_tech for login details.

### Apps

In the top left corner you can switch between different apps:

![](/files/2LKh6WeXLgabpHu89p3l)

* **Assets** is the main Digital Asset Management function.&#x20;
* **Entries** is a product management tool.
* **Insights** provides analytics information about the DAM usage
* **Portals** are mini websites (DAM as a CMS).&#x20;
* **Admin** is the admin functions across the whole site.  Not really an app, but that's where it is.

### Links

* [API Documentation](https://widenv2.docs.apiary.io/#)
* [Developer's API Blog](https://developer.widen.com/)&#x20;
* [API FAQs](https://community.widen.com/collective/s/article/API-FAQs)&#x20;
* [Widen Connect](https://community.widen.com/s/) (Support site)

#### API token

To create an API token:

Goto Admin --> Global settings --> API Setup --> New integration

Give your token a name and description (and you can create as many tokens as you wish).  You'll be prompted to associate the token with a user account, so select your own account for now.  Tokens are architected so that the account's role permissions are associated with each token. &#x20;

### Roles and asset groups

There are three [roles](https://community.widen.com/s/article/How-do-I-create-roles) set up : Site Admin, Uploader and General User. &#x20;

There are four [asset groups](https://community.widen.com/s/article/How-do-I-create-asset-groups): Public Assets, Restricted Assets, For Review Assets and Admin Only Assets.&#x20;

Asset groups and roles each have their own permission structure, and it is the relationship between roles and asset groups that form the basis of the granular, scalable governance model of Acquia DAM (a major differentiator among all other DAMS) as to which user roles can interact with which asset groups, and at what permission level.

### Metadata

There is a basic [metadata](https://community.widen.com/s/article/What-are-metadata-types) type (Widen refers to the metadata schema as a "type") named Primary Metadata Type.  When you upload files to the DAM you choose its type (and so the schema) which determines what field then need to be filled in.  A type may be 'copyrighted image' for example which who have fields like attribution to say who owns the image.

You may add fields to this metadata type, and you may add more metadata types. Again, scalable and configurable. &#x20;

From the Admin dashboard you may add more metadata [fields](https://community.widen.com/s/article/What-are-metadata-fields?r=0\&ui-knowledge-aloha-components-aura-components-knowledgeone.ArticleActions.handleEditPublished=1) to your metadata type (the more controlled vocabulary fields, the better), then later you can add additional metadata types (no limit to the number of types or fields within a type).&#x20;

### Upload profiles

There are four [upload profiles](https://community.widen.com/s/article/How-do-I-create-upload-profiles):  Public Assets, Restricted Assets, For Review Assets and Admin Only Assets.  These upload profiles are also permission controlled, and assign uploaded assets into their corresponding asset groups.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dxtech.tpximpact.com/learning-resources/acquia-dam-certification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.