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

# NOCK Customer Portal: Overview and Getting Started

> Share a project-specific portal so clients and stakeholders can submit feedback and track ticket status — no NOCK account required.

The NOCK Customer Portal gives you a shareable, project-specific link that you can hand to anyone outside your team — clients, beta users, project sponsors, or any other stakeholder. Visitors who open the link can submit feedback tickets and check the status of tickets on the project, all without creating a NOCK account. You stay in full control: the portal is scoped to a single project and exposes only what you choose to share.

## Who the Customer Portal is for

The portal serves two distinct groups:

**Operators** are NOCK team members who activate and manage the portal. If you run an agency and need to share progress with a client, or if you lead a SaaS product and want beta users to report bugs, you are the operator. You enable the portal in your project settings and distribute the generated link to whoever needs it.

**Portal visitors** are the external stakeholders who receive that link. They do not need a NOCK account, and they never interact with your internal dashboard. They simply open the URL, submit feedback, and check how tickets are progressing.

## What portal visitors can do

* Submit new feedback tickets directly from the portal
* View all tickets on the project and their current statuses
* Check back at any time using the same link

## What portal visitors cannot do

<Warning>
  The Customer Portal is intentionally limited to protect your team's internal workspace. Portal visitors have no access to:

  * Your internal NOCK dashboard or team settings
  * Internal comments, team notes, or private ticket details
  * Other projects in your NOCK workspace
  * Any connected integrations such as Linear
</Warning>

Visitors see ticket titles and statuses only. Internal discussion stays private to your team.

## Why use the Customer Portal

The Customer Portal is built for situations where transparency matters but full dashboard access is inappropriate:

* **Agency client work** — Let clients follow along with reported issues without giving them access to your internal tooling or other client projects.
* **Beta programs** — Give early users a simple way to report problems and feel heard, without requiring them to sign up for another tool.
* **Stakeholder updates** — Keep project sponsors or product owners informed on the state of feedback without scheduling manual status calls.

## Next steps

<CardGroup cols={2}>
  <Card title="Enable & Share the Portal" icon="link" href="/customer-portal/enable-share-link">
    Activate the Customer Portal for a project and copy the shareable link.
  </Card>

  <Card title="Submit Feedback" icon="message" href="/customer-portal/submit-feedback">
    Learn how portal visitors open the portal and submit a feedback ticket.
  </Card>
</CardGroup>