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

# Configure access and visibility

> Decide which teammates can reach which clients, and which apps each client can see.

Depending on your plan and operating model, you may need to configure which internal team members can access particular contacts or companies. You may also want different client users to see different apps or experiences based on their role, service, segment, or lifecycle stage.

## Internal team access

You can assign specific contacts or companies to individual internal team members. This is useful when several teammates serve different clients in the same workspace. See [Client access](/docs/core-concepts/client-access).

<Note>
  Client access requires an Advanced plan subscription.
</Note>

## Client-facing app visibility

Not every app needs to be visible to every client. Where it applies, configure custom visibility so clients only see the apps appropriate to their role, service, segment, or stage. See [Custom visibility](/docs/core-concepts/custom-visibility).

<Note>
  Customized app visibility is available only on select Assembly plans.
</Note>

## Before testing

<Check>
  Confirm which internal team members should have access to each contact or company.
</Check>

<Check>
  Review visibility for every client-facing app.
</Check>

<Check>
  Consider both who should receive access and when that access should begin.
</Check>

<Check>
  Test users with different roles, tags, or access levels — not only an all-access client.
</Check>