Some activities should not be visible for all AT users

[Michael_Soprano]

Multiple users would use one workspace - from different entities (companies)

Is it possible that:

1. Entity 1 employees see only entity 1 activities

1. Entity 2 employees see only entity 2 activities etc

Is it possible to do that using one workspace? 

Can it be done using properties? 

[purnimajena]

Hi @Michael_Soprano 

In Adobe Target, a single workspace cannot restrict visibility of activities by entity. All users assigned to that workspace will see all activities within it. To separate access by entity (so that Entity 1 only sees its activities, Entity 2 only theirs, etc.), you’ll need to use different workspaces and assign users accordingly.

Properties can be used to limit where an activity delivers on the site, but they don’t control activity visibility for users inside the same workspace.

[pradnya_balvir]

Hi @Michael_Soprano , Not possible to do using one workspace.

• In one workspace, all users see all activities. There’s no per-user/per-entity visibility filter inside a workspace.

• Properties only control where activities run (the site/app), not who sees them in Target UI.

So if you want:

• Entity 1 employees → only see/manage Entity 1 activities

• Entity 2 employees → only see/manage Entity 2 activities

Using Properties Effectively

Properties do help in a multi-entity setup, but for delivery, not governance:

• You can configure each entity’s website/app with its own property token in the Target library.

• Then you can assign activities to a property so they only run on the intended entity’s site.

• This prevents accidental cross-delivery (e.g., Entity 1 activity showing on Entity 2’s site).

But again, if both sets of users are in the same workspace, they’ll still see all activities in the UI — they just won’t all run everywhere.

Recommended Setup for Multi-Entity

If you’re running a multi-company / multi-brand Target account, the best practice is:

1. Separate Workspaces per Entity

   • Entity 1 → Workspace A

   • Entity 2 → Workspace B

   • Users are only added to their entity’s workspace.

2. Use Properties within Each Workspace (optional, but useful if entities have multiple sites/apps).

   • E.g., Entity 1 has Retail Site + Mobile App → properties split those environments.

This gives you both UI-level isolation (via workspaces) and delivery control (via properties).

Thanks.

Pradnya