> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nocknock.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Managing Team Members and Roles in Your NOCK Workspace

> Invite colleagues by email, assign Owner or Member roles, manage access, and remove team members from your NOCK project workspace.

The Team Members page is where you manage who has access to your NOCK workspace. You can invite colleagues by email, assign them a role that matches their responsibilities, and remove access when it's no longer needed. Because team membership is managed at the workspace level, everyone you invite gains visibility into all projects within that workspace.

## Inviting a team member

<Steps>
  <Step title="Open Team Members">
    From the NOCK dashboard, click **Team Members** in the left-hand navigation panel.
  </Step>

  <Step title="Click Invite Member">
    Click the **Invite Member** button in the top-right corner of the page.
  </Step>

  <Step title="Enter the email address">
    Type the email address of the person you want to invite. Make sure it matches the address they use to sign in to NOCK (or the address they will use when they create their account).
  </Step>

  <Step title="Select a role">
    Choose either **Owner** or **Member** from the role dropdown. See [Roles and permissions](#roles-and-permissions) below if you're unsure which to assign.
  </Step>

  <Step title="Send the invitation">
    Click **Send Invite**. NOCK sends the invitee an email with a link to join your workspace. The invitation appears as **Pending** in the team list until they accept.
  </Step>
</Steps>

<Note>
  Pending invitations can be cancelled at any time by clicking the **Revoke** button next to them in the team list — useful if you entered the wrong address or the invite is no longer needed.
</Note>

## Roles and permissions

NOCK has two roles at the workspace level: **Owner** and **Member**.

### Owner

Owners have full control over the workspace and every project within it. An Owner can:

* Access and manage all projects in the workspace.
* Invite and remove team members, and change their roles.
* Modify workspace-level settings.
* Change any project's settings, including deleting a project.
* Manage integrations (such as Linear).

<Warning>
  Every workspace must have at least one Owner at all times. If you are the sole Owner, you cannot demote yourself to Member until another Owner has been assigned.
</Warning>

### Member

Members can collaborate on feedback but have a more limited scope of control. A Member can:

* View and manage tickets across all projects in the workspace.
* Add internal comments to tickets.
* Change ticket statuses.
* View project settings (but not modify them).

Members **cannot** invite or remove other team members, change roles, adjust project settings, or delete projects.

<Tip>
  Assign the Owner role only to colleagues who genuinely need administrative control. Use the Member role for contributors who primarily triage and respond to feedback.
</Tip>

## Removing a team member

<Steps>
  <Step title="Find the team member">
    Locate the person you want to remove in the team members list.
  </Step>

  <Step title="Open the actions menu">
    Click the **⋯** (more options) button to the right of their name and role.
  </Step>

  <Step title="Select Remove Member">
    Click **Remove Member** from the dropdown menu. A confirmation dialog appears.
  </Step>

  <Step title="Confirm removal">
    Click **Remove** to confirm. The team member loses access to the workspace immediately. Any tickets, comments, or status changes they made are preserved.
  </Step>
</Steps>

<Note>
  Removing a team member does not delete any of their previous activity. Their comments and status changes remain visible in the ticket history.
</Note>

## Workspace-level vs. project-level access

NOCK manages team membership at the **workspace level**, not per project. This means:

* When you invite someone to the workspace, they can see **all projects** in that workspace — there is no way to restrict a team member to a single project.
* If your organisation needs strict separation between projects, consider creating separate workspaces for each product or team.

<Tip>
  Keeping related projects together in one workspace makes it easy to share team members across them without re-inviting anyone. Use workspace separation only when access isolation is a firm requirement.
</Tip>

***

<CardGroup cols={2}>
  <Card title="Project Settings" icon="sliders" href="/dashboard/project-settings">
    Configure widgets, integrations, and project lifecycle options.
  </Card>

  <Card title="Tickets" icon="list" href="/dashboard/tickets">
    View and manage all feedback tickets submitted to your project.
  </Card>
</CardGroup>