Manage campaign members

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

Campaign settings - granting different access rights

	Campaign Owner	Member	Member Restricted
Send messages with the campaign	Yes	Yes	Yes
Manage users and system integrations	Yes	No	No
View all messages sent	Yes	Yes	Only view messages sent by restricted member. Not able to view messages sent by other members in the campaign.

For agency officers without a .gov.sg email domain, you will need to get .gov.sg email domain from your parent ministry.

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

   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 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