Project settings

To change the project's name, open a project in Assets and choose Settings → General in the sidebar. Under Identity, edit the Project name, Slug (lowercase letters, numbers and hyphens) or Description. Each one saves when you leave the field or press Enter.

These belong to the project itself, which your organization shares across the suite, so a new name shows in Dash and every app that opens the project.

Identifiers lists the read-only Project ID and DAM project ID, with copy buttons, for API and support use.

The Delivery section of Settings → General has two switches for the project's public delivery addresses. Both save as you change them.

• URL transforms: lets delivery addresses resize, crop, convert and apply effects to images. Off, the default, serves originals only and refuses transform addresses.
• Deliver new assets by default: new uploads start with delivery turned on, so their addresses work straight away. Existing assets keep their own setting. On by default.

The limits on transforms and who can load addresses are in Platform → API → Delivery Settings. See Delivery.

Settings → Add-ons lists the optional screens you can turn on for the project, such as Brand Kit, Watermarks and Contact Sheets, each with a switch. Turning one on adds its entry to the sidebar. See Add-ons.

Settings → Usage & Storage shows what the project uses. The figures across the top show Storage used against the quota, the number of Assets, Bandwidth over the last 30 days and recent Transforms. Charts show Storage growth over 30 days, storage By file type and the Largest folders.

Under Limits & retention:

• Storage quota: the project's storage in GB, 500 to start. The project overview's Storage Usage gauge and Storage available check measure against it.
• Quota alert threshold: a percentage of the quota, 80% to start. When an upload takes the project past it, workflows with the Storage threshold crossed trigger run.

The quota is a target for these figures and workflows; Assets doesn't stop uploads when you pass it. See Workflows.

Roles decide what each person on the project's team can do in Assets. To see them, choose Settings → Permissions & Security; the Roles tab lists each role with its description, permissions and how many people hold it. Governance → Permissions opens the same screen.

Five built-in roles come with every project, marked System role:

• Owner: everything, including billing.
• Admin: everything except billing, including deleting assets and managing settings, the team and roles.
• Manager: memberships and assets, and inviting and assigning people, but can't delete assets or edit roles.
• Member: day-to-day work, including editing and uploading assets.
• Viewer: the project overview and analytics only.

People get the role matching their organization role: Owner, Admin or Manager, and Member for everyone else. Change someone's role on Collaboration → Team; see Collaboration.

To make your own role, choose New role on the Roles tab, or Duplicate on an existing one to start from its permissions.

1. Type a Name and a Key, a short unique ID. Both are required.
2. Optional: add a Description and pick a Colour.
3. Select the permissions it grants. Each group has a box that selects or clears the whole group.
4. Choose Create role.

Assets checks these permissions when someone acts:

• Edit an asset: uploading and replacing files.
• Delete an asset: deleting assets and deleting them permanently from the trash.
• Manage settings: creating and changing retention policies and legal holds.
• Governance, under the view permissions: seeing retention policies and legal holds.

Built-in roles can't be edited or deleted, only duplicated. A custom role can be deleted once nobody holds it.

The bottom of Settings → Advanced holds three actions, and Assets asks you to confirm each one.

• Reset settings to defaults: returns the project's Assets settings to their defaults, including the storage quota and add-ons, which go back to Brand Kit only. It also empties Brand Kit, Watermarks and Contact Sheets.
• Transfer project: moves the project to another Target organization, chosen from the organizations among your projects.
• Delete project: deletes the whole project, which Dash and the other apps share, not only its assets. Type the project's name to confirm. Assets then takes you out of the project.

Transferring and deleting change the project for every app in the suite, so check with your organization's admins first. Managing projects is otherwise done in Dash.