Collaboration

A shared link lets people outside the project see an asset or a collection without signing in. To create one, open a project in Assets, choose Collaboration → Shared Links in the sidebar, then New link.

1. In Link name, type a name you'll recognize later. It's required.
2. In Shares, choose A single asset or A collection, then pick it in the field beside it.
3. In Expires, choose Never expires, In 7 days, In 30 days (the default) or In 90 days.
4. Choose Create link. The link is live straight away.

To send it, choose Copy URL in the link's ⋯ menu, or click its row. The page it opens shows the shared files' thumbnails, names and types, and the date access ends; it has no download button. A shared collection shows the assets in it when the page is opened.

You can also share one asset from the Asset Library: Share → Create share link in its ⋯ menu makes a link that expires in 30 days and copies it for you.

The figures across the top of Shared Links count Active links (with the total), Views and Downloads, and the links Expiring soon, within 7 days. A link counts a view each time someone opens its page.

Each row shows the link's name and what it shares, its status, when it expires (in amber when that's within 7 days), its views and the date it was created. Filter by status, or search by link name and the shared asset or collection.

Each row's ⋯ menu has these actions:

• Copy URL and Open.
• Edit: change the name, what it shares and when it expires.
• Revoke: the URL stops working at once, and the link stays in the list as Revoked.
• Delete: Assets asks first, then the URL stops working and the link and its view count are gone.

A link also stops working once its expiry date passes. Anyone opening a revoked, expired or deleted link sees "This link isn't available".

A review routes work through an approval pipeline until it's approved or rejected. You need an active pipeline for the kind of work first; see Creating an approval pipeline. Then choose Collaboration → Approvals in the sidebar and Request review.

1. In Review name, type a name. It's required.
2. In Reviewing, pick the kind of work, such as Asset, Collection, Shared link or Payout. Asset is the default.
3. In Pipeline, pick one of the active pipelines for that kind of work. The default pipeline is picked for you.
4. Set Priority (Low, Normal, High or Urgent; Normal to start) and Due (No due date, In 3 days, In a week or In two weeks; In a week to start).
5. For an asset review, select the assets to review in Assets. At least one is required.
6. Choose Request review.

The review starts In Review at the pipeline's first stage. It keeps its own copy of the pipeline's stages, so editing the pipeline later doesn't change reviews already under way. Only asset reviews carry items; reviews of other kinds of work hold the decisions and discussion on their own.

Every review has one status, shown on the Approvals list and in the review:

• In Review: waiting on its current stage. New reviews start here.
• Changes Requested: sent back. It stays on the same stage, and approving again picks up from there.
• Approved: the last stage signed off.
• Rejected: someone rejected it, which closes it.
• Cancelled: someone cancelled it from the list.

Approved, Rejected and Cancelled reviews are finished. Choose Reopen in a finished review to put it back In Review on the same stage. A review is overdue once its due date passes while it's still open.

Click a review on the Approvals list to open it. Its Approval route shows each stage, who it's for and how many approvals it still needs.

• Items: for an asset review, each asset has buttons to approve it, request changes on it or reject it. These per-item decisions save straight away.
• Decision: add an optional note, then choose Approve stage, Request changes or Reject. Request changes appears only when the stage allows change requests. In an asset review, decide on at least one item before you approve the stage.

Each approval counts toward the stage's minimum. Once a stage has enough, the review moves to the next stage, and after the last one it's Approved. When a review is approved, its assets are set to Approved, unless the pipeline's Mark the subject approved setting is off.

Decision history lists every decision with its note. Discussion holds the review's comments: write one and choose the send icon, reply to a thread, or Resolve it.

The figures across the top of Approvals count reviews In flight, those that Need changes, the ones Approved, and those Overdue.

Each row shows the review's name, the kind of work and its number of items, its pipeline, the stage it's on (such as 1 of 2), its priority, status and due date, in red when overdue. Filter by status and by kind of work, or search by name and pipeline.

Each row's ⋯ menu has Open, Cancel for a review that isn't finished, and Delete. Delete asks first, and the review's decision history goes with it; cancel instead to keep the record.

An approval pipeline is the route a kind of work follows to sign-off, one stage after another. To create one, choose Collaboration → Approval Pipelines in the sidebar, then Create pipeline.

1. Type a Pipeline name. It's required.
2. In Applies to, pick the kind of work it routes, such as Asset, Collection, Shared link, Role grant or Payout.
3. In Start from, pick Blank pipeline or a starter: Brand review, Client delivery, External access or Finance sign-off.
4. Choose Create pipeline.

The pipeline is created as a Draft. Open it to set its stages, then choose Activate; only active pipelines can take new reviews. Pause stops new reviews without touching reviews under way.

Open a pipeline from Approval Pipelines to edit it. Changes save as you make them.

• General: the pipeline's Name, Description and Applies to, and Default pipeline, which makes it the one picked first when someone requests a review of that kind of work.
• Approval route: choose Add stage for each step. Give each stage a name, then in Who approves choose Anyone with a role and a Role, or Specific people and the People. Set Minimum approvals, and turn Allow change requests on or off. Move stages up or down, or remove them.
• On final approval: Mark the subject approved sets a review's assets to Approved when the last stage signs off. It's on by default.

To activate a pipeline, it needs at least one stage, and every stage needs an approver. Delete pipeline asks first; reviews already under way keep their own copy of the stages. The ⋯ menu on the pipeline list also has Edit, Duplicate, Make default and Delete.

Collaboration → Comments & Activity collects the project's conversations and a log of what happened. The figures across the top count Open threads, Replies, Resolved threads and Events today.

• Comments: every thread from review discussions. Filter by All Threads, Open or Resolved, search them, reply, and choose Resolve or Reopen.
• Activity: who did what and when, newest first and grouped by day, covering shared links, review requests and decisions, and comments. Filter by All Activity, Assets, Sharing, Approvals, Comments or Team, or search.

Collaboration → Team lists the people with a role in the project in Assets, on its Members tab, with each person's role and the date they joined. Search by name, email or role.

• Sync from org adds everyone in your organization who isn't on the team yet. Each person gets the role matching their organization role: Owner, Admin or Manager, and Member for everyone else.
• Role: pick a different role for someone in their row. It changes straight away and decides what they can do, such as whether they can delete assets.
• Remove from workspace, in a person's ⋯ menu, asks first. They lose their role in the project and can no longer upload, download or delete its files. What they created stays.

People in your organization also join the team with their matching role the first time they work with the project's files. Someone you removed isn't added back that way. Roles and their permissions are set under Settings → Permissions & Security; see Project settings.