---
title: "Manage campaign access"
slug: "manage-campaign-access"
abstract: "A user who is not yet a member of a campaign can send a request to admins to join the campaign."
---
# Manage campaign access

SitecoreAI  lets teams control who can access and collaborate on campaigns. Users can request to join a campaign, while admins can review and approve or deny those requests. Admins and existing campaign members can also add members directly.

## Permissions to manage campaign membership

Campaign membership is managed through three Stream app roles: *Admin*, *User*, and *Read-only*. Each role determines what actions a user can perform.

- **Add members** - admins and campaign members with the *User* role can add people to a campaign by clicking the **Add members** :mdiPlusCircleOutline: icon in the top-right corner of the overview campaign page. They can then search for users by name or email. Admins can also approve requests to join a campaign.
![Click Create campaign on the Campaigns page](https://doc.sitecore.com/api/markdown-image/sai/en/users/sitecoreai/images/sai-add-remove-campaign-members.png) 
- **Remove members** - admins can remove anyone, including themselves and other admins. Campaign members with the *User* role can remove other members, but not admins. Users with the *Read-only* role cannot remove members. To remove someone, click the member avatars in the top-right corner of the page, then click :mdiTrashCan: next to their name.
    > [!note]
    > Members removed from a campaign appear as *User removed* in task assignments. Users removed from the organization are labeled as *Unknown User*.
- **Assign tasks** - admins and campaign members with the *User* role can assign tasks to people who aren't campaign members. These users are automatically added to the campaign when assigned a task.
- **Tag users in comments** - admins and campaign members with the *User* role can mention non-members in comments. When you tag someone who isn't a member, you're prompted to add them to the campaign.


## Request to join a campaign

Users who are not members of a campaign can request to join directly from the campaign overview page. Requests do not expire and remain pending until an admin takes action. This feature complements the existing ability for admins and existing campaign members to add other members manually.

To request to join a campaign:

1. In the navigation menu, click **Strategy**. 
2. In the left sidebar, click :mdiBullhornVariantOutline: **Campaigns**.
3. On the **Campaigns** page, click the name of the campaign you want to join.
4. Click **Request access**.
5. In the **Request to join** dialog, optionally enter a reason for joining, then click **Send request**.

After you submit your request:

- All admins receive a notification, even if they're not campaign members.
- A pending request message appears on the campaign overview page and in the campaign list.
- You're notified when an admin approves or denies your request.
- If approved, you gain access to the campaign's details and collaboration features.

## Approve or deny a join request

Admins can review and respond to join requests from either the **Notifications** dialog or the campaign's **Details & settings** tab. When an admin responds, the request notification is removed for all other admins.

### From Notifications

To approve or deny a join request in the **Notifications** dialog:

1. In the navigation menu, click the **Notifications** :mdiBellOutline: icon. 
2. Find the join request and click **Accept** or **Deny**.

### From Details & settings

To approve or deny a join request on the **Details & settings** tab:

1. In the navigation menu, click **Strategy**. 
2. In the left sidebar, click :mdiBullhornVariantOutline: **Campaigns**.
3. On the **Campaigns** page, open the relevant campaign.
4. On the **Details & settings** tab, find **Members requests**.
5. Click **Accept** or **Deny** next to the request.

After an admin responds, the requester receives a notification. Approved users appear in the campaign's members section, while denied users can submit another request later.