User Sharing¶

User Sharing lets you control who can access your configurations, scenarios, and cookies in the Waulter dashboard. You can share with individual team members, agency clients, or entire organisations — without giving everyone access to everything.

There are two sharing modes: local sharing (share a single configuration) and global sharing (share all configurations under a partner).

Two sharing modes¶

Local sharing (per-configuration)¶

Local sharing grants a specific user access to a single configuration. Use this when you want fine-grained control over who sees what.

Use cases:

• Share your DEV configuration with developers, but keep PROD restricted to ops — see DEV & Testing Workflow
• An agency shares a specific client configuration with that client's marketing manager
• Grant a colleague access to one site without exposing your entire portfolio

How to share locally:

1. Open the configuration in the Waulter dashboard.
2. Navigate to the Sharing section.
3. Enter the target user's email address.
4. Select the role (read or admin).
5. Click Share.

The target user immediately sees the configuration in their dashboard.

Global sharing (per-partner)¶

Global sharing grants a user access to all configurations under a partner — including any configurations created in the future. This is a persistent rule, not a one-time action.

Use cases:

• An agency shares everything with a client's account manager who needs visibility across all sites
• A company gives a new team member access to all configurations at once
• Waulter support staff need access to all configurations for troubleshooting

How to set up global sharing:

1. Open the Partner section in the dashboard.
2. Navigate to Global Sharing.
3. Enter the target user's email address.
4. Select the role (read or admin).
5. Click Add Global Share.

Comparison¶

Roles¶

What gets shared (cascade)¶

When you share a configuration — locally or globally — permissions automatically cascade to related entities:

flowchart TD
    A[Share a Configuration] --> B[Partner metadata]
    A --> C[All cookies under the configuration]
    A --> D[All tied scenarios]

    D --> E{{"Tied = scenario references this config<br/>as fallback or in a rule"}}

    style A fill:#4051b5,color:#fff
    style B fill:#e8eaf6,color:#333
    style C fill:#e8eaf6,color:#333
    style D fill:#e8eaf6,color:#333

Global sharing cascade¶

When you add a global share, the cascade runs across all active configurations under the partner:

1. Every active configuration under the partner receives the user's permission
2. Each configuration's cookies and tied scenarios are also shared
3. Any new configuration created under this partner in the future is automatically shared with the user

Self-removal¶

A user who has been given shared access can remove themselves from a configuration they don't own. This is useful when:

• A team member changes roles and no longer needs access
• A client wants to revoke their own access after a project ends
• Preparing for a Transfer of Ownership

Self-removal does not require admin permission — any shared user can remove themselves.

Removing shared access¶

Removing a local share¶

The configuration owner (or any user with admin role) can remove a user's local access:

1. Open the configuration's Sharing section.
2. Find the user in the access list.
3. Click Remove.

The user immediately loses access to the configuration and its cascaded entities (cookies, tied scenarios).

Removing a global share¶

When removing a global share, you have two options:

Audit trail¶

Every sharing operation creates an immutable event log entry. This provides a complete history of who shared what, with whom, and when.

Logged events include:

• Share (local and global)
• Unshare (local and global)
• Self-removal
• Role changes

Each event records:

• Who initiated the action
• The target user
• The role granted or revoked
• Which configurations and scenarios were affected
• Timestamp

Best practices¶

Troubleshooting¶