> For the complete documentation index, see [llms.txt](https://postman-v2.guides.gov.sg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://postman-v2.guides.gov.sg/general-users-ui-portal/campaign-settings/manage-campaign-members.md).

# Manage campaign members

Learn about the three types of access rights to Postman campaigns. 

<figure><img src="https://862051585-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl3mC1ibWq8HG4BKl4qlL%2Fuploads%2Fvbm6nCKKJqjksTcvpUXP%2FScreenshot%202024-11-27%20at%202.51.54%E2%80%AFPM.png?alt=media&amp;token=64b71e94-5708-4b30-a689-dd2ffa92b16c" alt="" width="375"><figcaption><p>Campaign settings - granting different access rights</p></figcaption></figure>

<table><thead><tr><th width="232"></th><th width="181">Campaign Owner</th><th width="126">Member</th><th>Member Restricted</th></tr></thead><tbody><tr><td>Send messages with the campaign</td><td>Yes</td><td>Yes</td><td>Yes</td></tr><tr><td>Manage users and system integrations<br></td><td>Yes</td><td>No</td><td>No</td></tr><tr><td>View all messages sent</td><td>Yes</td><td>Yes</td><td>Only view messages sent by restricted member. Not able to view messages sent by other members in the campaign.</td></tr></tbody></table>

**Why is Campaign Creator not included as a role under Members?**

* Campaign Owner and Campaign Member are campaign-specific roles. They control what a user can do inside a specific campaign.
* [Campaign Creator](https://postman-v2.guides.gov.sg/general-users-ui-portal/request-for-campaign-creation-rights-from-agency-pics) is not a campaign-specific role, rather it is a Postman role.
  * A campaign creator merely has the permission to create campaigns on Postman. This permission is granted by agency PICs.

To read more FAQs regarding the abilities of Campaign Creators and Owners, please click [here](https://postman-v2.guides.gov.sg/general-users-ui-portal/faqs-ui-portal).

{% hint style="info" %}
For agency officers without a `.gov.sg` email domain, you will need to get `.gov.sg` email domain from your parent ministry.
{% endhint %}

### What are some special cases?

1. **Non `gov.sg` domains that are considered government entities**
   1. For now, this is limited to `aic.sg`, `synapxe.sg`, `edu.sg` *(Polytechnics and ITE only)*
   2. \*By default, every user with this domains has *member* access rights.
   3. Users with these domains who need **admin access** (i.e. can create campaigns, access and amend campaign settings) must request for specific email address whitelisting *through the agency PIC.*
   4. Otherwise, all users with these domains can already log into Postman and view campaigns they have been added to (i.e. member access)
2. **Vendors helping government entities with API integrations**
   1. In such cases, Postman will *not* be granting vendors access to the portal. This means vendors with non-whitelisted email domains cannot log into Postman.
   2. Agency officers should log into Postman, create the campaign and craft the message, whitelist the IP addresses, generate the API keys and pass the API keys to the vendors for the necessary integration.
3. **Vendors helping government entities send messages on Postman UI**
   1. In such cases, agency PICs must [submit a request](https://form.gov.sg/657025a2d2bd350012c82eb0) for the Postman team to whitelist the vendor's domain. This will allow vendors to log into Postman, and view campaigns that the vendors have been added to by the agency admins.
   2. Vendors will then be able to log in and send messages, but ***not*** create campaigns i.e. member access


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://postman-v2.guides.gov.sg/general-users-ui-portal/campaign-settings/manage-campaign-members.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.