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

# Customer Portal

> Share selected project work with customers and manage their access.

The Customer Portal gives customers a place to review shared work, comment, and provide the information your team needs. They sign in with their invited email address without joining your internal Quivly workspace.

Two controls determine what someone can see: their access to the **project** and the **visibility of each task**. Review both before inviting people.

## Share a project

<Steps>
  <Step title="Choose the visible work">
    Open a customer project and select **Share**. Under **Task visibility**, enable the tasks your customer should see. Review their descriptions and any customer-visible comments or files.

    Task visibility applies to people with access to this project. Hiding a task removes it from their portal, including access through a direct link. Manage milestone visibility in the project controls when you want customers to see those checkpoints.
  </Step>

  <Step title="Add people">
    Select **Add people**, then choose a customer contact or enter an email address. Adding someone grants project access and requests an invitation email immediately. **Done** closes the dialog.
  </Step>

  <Step title="Check access">
    Review **People with access**. People appear as **Invited** until they sign in, then **Active**. If an invitation has not arrived, check the email address and use **Resend invitation** from that person's menu.
  </Step>
</Steps>

## Preview a customer's view

In the person's menu, select **View as this user**. A new tab opens a read-only preview using their access, including which projects and tasks are visible.

Use this preview to check the shared experience. Comments and status changes are disabled in the portal preview.

<Note>
  The portal preview is different from **Preview as customer** on a task form. The form preview opens the live published form, and submitting it records a real response. See [Task Forms](/product/task-forms#preview-the-published-form).
</Note>

## What customers can do

Customers open their invitation, enter their invited email address, and verify the code sent to that address. If prompted, they choose the account they want to access.

Within their shared projects, customers can read visible work and customer-visible comments, add comments to open tasks, and submit published [task forms](/product/task-forms).

They can also mark their team's side of an open task done and retract that signal while the task remains open. This records customer completion; your team controls the internal task status separately. An incomplete attached information request must be completed first. Closed tasks are read-only.

## Remove access

Open **Share**, find the person, and choose **Revoke access**. Confirm the action, then check the updated access list.

Revoking access removes this project from that person's portal. Other projects shared with them remain available. Removing their last project grant also ends their portal sessions.

Hiding a task is useful when you want to remove access to that item while keeping the rest of the project shared.

## Troubleshooting

<AccordionGroup>
  <Accordion title="Why does the customer see an empty project?">
    Check that they have access to the intended project and that the tasks are customer-visible. Project access alone does not make every task visible. Use View as this user to inspect the result.
  </Accordion>

  <Accordion title="Why hasn't the invitation or sign-in code arrived?">
    Confirm the invited email address and ask the recipient to check their spam folder. Resend the invitation if needed. The customer must sign in with the address that has project access.
  </Accordion>

  <Accordion title="What should I do if sharing or revoking access shows an error?">
    Reopen Share and check the current access list before retrying the indicated action. Access changes and notification delivery can have separate outcomes.
  </Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.