Skip to main content

Map control information and evidence across Workspaces (New experience)

Learn how to map control info, policies, and evidence across Workspaces in the new Drata experience and manage shared controls efficiently.

Updated this week

💡 Still using the classic Drata experience? Refer to Linking Control Info & Evidence Across Workspaces for the original UI.

What mapping controls across Workspaces does

Mapping controls across Workspaces lets you share control information, policies, and evidence for the same control across multiple Workspaces.

This is useful when:

  • You manage multiple products or business units

  • The same control applies across Workspaces

  • You want to avoid duplicating evidence and policies

When controls are mapped, updates made in one place apply everywhere that control is mapped.


What can be mapped

Only the following control sections can be mapped across Workspaces:

  • Control info

  • Policies

  • Evidences

Important: Miscellaneous Evidence cannot be mapped across Workspaces.


Prerequisites

  • Workspaces must be enabled.

  • You must have one of the following roles:

    • Admin

    • Workspace Manager

    • Control Manager

    • Information Security Lead


Workspace Manager limitations

Workspace Managers have additional restrictions:

  • Workspace Managers assigned to only one Workspace cannot map controls across Workspaces.

  • Workspace Managers can map or unmap only the Workspaces they’re assigned to.


How control mapping works

Controls can be mapped only if the same control code exists in multiple Workspaces.

Mapping creates a control group. Within that group, you can:

  • Share control info

  • Map policies

  • Map evidence

  • Unmap a Workspace later to make the control independent again


Map controls across Workspaces

  1. Go to the Controls page.

  2. Select a control that exists in multiple Workspaces.

  3. Add or remove Workspaces in the Mapped Workspaces section.

Result: The control info is now mapped across the selected Workspaces.

Policies can only be mapped across Workspaces after the control itself has been mapped (grouped).


Map evidence from the Evidence Library

Rule: You can map only existing evidence. You can’t create new evidence during this process.

  1. Go to the Controls page.

  2. Select a control that exists in multiple Workspaces.

  3. Go to the Evidence tab.

  4. Select Add under Evidence Library.

  5. Select the evidence and continue.

  6. Choose the Workspaces to map.

  7. Select Save.

Result: The evidence is shared and reusable across all mapped Workspaces.


How shared evidence behaves

When evidence is mapped across Workspaces:

  • It can be reused indefinitely in those Workspaces

  • Updates apply to all mapped controls

  • It behaves similarly to shared policies

Important: Updates to shared evidence may impact the readiness of all controls mapped to it.


Update evidence mapped across Workspaces

You can update mapped evidence either:

  • From a control, or

  • Directly from the Evidence Library


Update from a control

  1. Go to the Controls page.

  2. Select a control that exists in multiple Workspaces.

  3. Expand Evidence Library under Control evidence.

  4. Select the Update icon.

  5. Save your changes.


New Monitoring & Controls experience (Early Access)

If you’re using the new Monitoring & Controls experience:

  • The Update icon isn’t available on the Control page.

To update evidence manually:

  1. Open the Control page.

  2. Select the Evidence tab.

  3. Select the evidence.

  4. Choose Update dates.

  5. Update the Creation or Renewal date.


Unmap a Workspace from a control

At any time, you can remove a Workspace from a control group.

When you unmap a Workspace:

  • The control becomes its own independent instance

  • Previously shared updates no longer apply


Summary

Mapping controls across Workspaces helps you:

  • Reduce duplication

  • Maintain consistency

  • Update evidence and policies once instead of multiple times

This feature is designed for teams managing shared compliance requirements across multiple Workspaces.

Did this answer your question?