> For the complete documentation index, see [llms.txt](https://docs.smaq.io/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.smaq.io/documentation/organization/members.md).

# Members & invitations

Every SMAQ organization has its own list of members. Org membership is the prerequisite for accessing any project in the org. Project-level [member roles](/documentation/projects/manage-project-members/member-roles-and-access.md) are managed separately.

> **\[Screenshot needed]** Organization Settings → Members tab showing the member list with org roles and Last active timestamps.

### Org-level roles

There are two roles at the organization level:

| Role       | Permissions                                                                                                                  |
| ---------- | ---------------------------------------------------------------------------------------------------------------------------- |
| **Owner**  | Manage billing, all members, all projects, org-level settings.                                                               |
| **Member** | Has org membership (required for project access) but can't change org settings. Project-level access controlled per-project. |

Most people are org Members. Owners are usually founders and the billing-responsible person.

### Inviting an org member

1. Open the **Organization Settings** page (your org name in the top nav → **Settings**).
2. Click the **Members** tab.
3. Click **Invite member**.
4. Enter email, pick org role (Owner or Member).
5. Send.

The invitee receives an email and joins the org once accepted.

> **\[Screenshot needed]** Invite Member dialog with email field and role dropdown (Owner / Member).

### After invitation

Org members don't automatically have access to any projects. You (or another project Owner/Editor) need to invite them to specific projects. See [Invite team members](/documentation/projects/manage-project-members/invite-team-members.md).

The two-step model (org invite, then project invite) is intentional: it lets you have teammates in the org without giving them access to every client/brand the org manages.

### Changing org roles

1. Organization Settings → Members.
2. Click a member.
3. Change role.

Promoting a Member to Owner gives them billing access. Be deliberate.

### Removing an org member

1. Organization Settings → Members.
2. Click the member → **Remove from organization**.

Removing them also removes them from every project in the org. Their direct work (dashboards they created, chat history) is preserved with their name attached.

### Re-inviting

If someone left and rejoins, re-invite them. They'll create a new membership; their previous chat history and work attribution remain in place.

### Pending invitations

The Members tab also shows pending invitations with **Resend** and **Revoke** options. Invitations expire after 7 days.

### Tips

* **Don't make everyone an Owner.** Billing access is sensitive.
* **Audit periodically.** Quarterly check of org membership to remove ex-teammates.
* **For client access, skip org membership.** Invite clients directly to specific projects as [Viewers](/documentation/projects/manage-project-members/member-roles-and-access.md) — they don't need org access.

### Related

* [Member roles and access](/documentation/projects/manage-project-members/member-roles-and-access.md) — project-level roles.
* [Billing & usage](/documentation/organization/billing-and-usage.md) — controlled by org Owners.


---

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

```
GET https://docs.smaq.io/documentation/organization/members.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.