Curate projects
Curation lets you limit the components (dimensions, metrics, segments, date ranges) before sharing a project. When a recipient opens the project, they see a limited set of components that you have curated for them. Curation is an optional but recommended step before sharing a project.
See
Apply project curation
- Select Share > Curate Project Data.
The components that are used in the project are automatically added.
If a project has multiple report suites, you see a curate drop target for each report suite in the project. - (Optional) To add more components, drag components you want to share from the left panel to the Curate components drop zone for the data view.
- Select Done.
When a recipient opens a curated project, they only see the curated set of components you have defined:
Remove project curation
To remove project curation and restore the full set of components in the left rail:
- Select Share > Curate Project Data.
- Select Remove Curation.
- Select Done.
Virtual report suite curation
To apply curation at a report-suite level, so that it applies to many projects at once, you can curate components in a Virtual Report suite.
Component curation options
In a curated project or virtual report suite, the recipient is presented with the option to Show All components in the left rail. Show All reveals different sets of components, depending on:
- The user鈥檚 permission level (admin or non-admin)
- Project role (owner/editor or not)
- Type of curation applied (Virtual report suiteS or project)
- Components owned by or shared to the user. Owned/shared components include segments, calculated metrics, and date ranges. They do not include implemented components, such as eVars, props, and custom events.
Note: Non-admin view roles do not have access to the left rail in a project, so they have been omitted from the table below.