> For the complete documentation index, see [llms.txt](https://playbook.nativemsg.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://playbook.nativemsg.com/get-started/knowledge-base/knowledge-base/create-account-+-add-users.md).

# Create Account + Add Users

## Creating and Managing Accounts

**Goal:** Set up your nativeMsg account, invite your team, and manage sub-accounts with the right permissions.\
**Estimated Time:** 10–15 minutes

***

### What This Covers

* Creating your main account
* Adding and managing sub-accounts (team users)
* Updating or removing users
* Permissions and access control

***

### ✨ Overview

Each organization on nativeMsg starts with a **main account** (the admin) — usually your primary onboarding contact. From there, you can add **sub-accounts** for teammates who need access to Bots, Conversations, Blasts, and other sections of the platform.

> 💡 *Think of sub-accounts as team user profiles — each with their own login and permissions.*

***

### 🆕 Creating Your Main Account

1. **Check your email for an invitation from nativeMsg.**\
   Your Customer Success Manager will send this during onboarding.
2. **Click “Accept Invitation.”**\
   This link will take you to your organization’s nativeMsg login page.
3. **Create your password.**\
   Use a strong, unique password.

   > 💡 *For security, do not reuse credentials from other platforms.*
4. **Confirm your organization details.**\
   Check that your company name and email domain are correct.
5. **Log in to your dashboard.**\
   Once inside, you’ll see your **Settings** menu — this is where you’ll manage users and permissions.

***

### 👥 Adding Sub-Accounts (Team Users)

A **sub-account** is a user you create in nativeMsg with customizable permissions.\
Sub-accounts are ideal for teammates who handle specific areas like campaign management, compliance, or development.

#### Steps to Add a Sub-Account

1. Go to **Settings → Manage Sub-Accounts**.
2. Click **New Sub-Account**.
3. In the **Create Sub Account** window, enter:
   * Full name
   * Email address
   * Role (optional)
4. Click **Save**.

✅ *The new sub-account is now active and, by default, has full access permissions.*

> 💬 *You can customize permissions right after adding the user.*

***

### ✏️ Updating Permissions

Each sub-account can have different access levels for platform features such as Bots, Conversations, and Blasts.

1. Go to **Settings → Manage Sub-Accounts**.
2. In the **Search Sub Account** field, enter the user’s name.
3. Click **Update**.
4. Under **Permissions Settings**, use the **Update Sections** dropdown to:
   * **Select All** → grant full access
   * **Deselect All** → remove all access
   * Or choose specific modules to allow (e.g., Conversations, Blasts)
5. Click **Done** to save.

> ⚙️ *Example: Give your marketing team access to Blasts, while limiting configuration access to admins.*

***

### ❌ Deleting a Sub-Account

If someone leaves your organization or no longer needs access:

1. In **Settings → Manage Sub-Accounts**, search for the user.
2. Click **Delete Sub Account.**
3. Confirm by clicking **Yes** in the pop-up message.

🚨 *Deleting a user immediately removes all permissions and access.*

***

### 🔍 Searching for Users

* Use the **Search Sub Account** field to find users.
* Type at least 3 characters to see matching results.
* Click inside the field to view all existing sub-accounts.

***

### ✅ Checklist

* [ ] Main account created and verified
* [ ] Password set
* [ ] Team members added as sub-accounts
* [ ] Permissions reviewed and customized
* [ ] Unused accounts deleted

***

### 💬 Need Help?

If you run into any issues or have questions about permissions, reach out to your Customer Success Manager or email **<support@nativemsg.com>**. We’re happy to guide you through user setup or access configuration.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://playbook.nativemsg.com/get-started/knowledge-base/knowledge-base/create-account-+-add-users.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.