> ## Documentation Index > Fetch the complete documentation index at: https://docs.d0pam1ne.blackhatethicalhacking.com/llms.txt > Use this file to discover all available pages before exploring further. # Clients and groups > Set up client companies and their users, and scope exactly what each one sees. A **client** in Synapse is a person at a customer organization who signs in to the portal to see and fix their own issues. Clients are organized into **companies**, and their access is scoped so each one sees only what you grant, down to a single issue. ![The Synapse Clients list, grouped by company](https://mintcdn.com/black-hat-ethical-hacking/OoWrmGEHoSIMtvDf/images/synapse/clients-list.webp?fit=max\&auto=format\&n=OoWrmGEHoSIMtvDf\&q=85\&s=3fcdbe70bfa341ecbf3ce6c6cb39e590) The Clients list: users grouped by company, each with Resend welcome, Edit, Suspend and Remove, plus Preview portal. ## Companies and users Rest the mouse on a company card or a client user to preview it: the company card shows each user, where they sign in from and the open and overdue work across its projects; a user shows how they sign in and what they can see. Open **Synapse, Clients**. A company is the customer organization; its users are the people who sign in. To add several people from the same customer, pick the existing company from the list instead of retyping it, so they land under one roof. The **Cards** view shows each company as a card: its users, how many are active and on two-step login, any pending invites, the projects or groups it can see, and its open and overdue work, so you can tell at a glance which customer needs chasing. Click a card, or switch to **List**, for the users themselves. Each client user carries a name, an email and the scope you give them. You can: * **Edit** a user's contact details at any time. * **Suspend** a user to revoke their portal access, then **restore** it later. Their issues and messages are kept throughout, nothing is lost. * **Resend the welcome** to a user who never finished setup or lost their link, which issues a fresh invite without creating a second account. * **Generate a new password** with **New password**, for a user who never got or lost their email: Synapse mints a fresh one-time password (emailed to them automatically when they have an address on file, otherwise shown once to copy) and signs out their old sessions. A strip above the companies shows the [weekly digest](https://docs.d0pam1ne.blackhatethicalhacking.com/synapse/weekly-digest.md): how many clients get it and when the next one goes out. In the list, subscribers carry a **Weekly digest** tag and **Preview digest** shows this week's email exactly as that client would get it. Clients turn the digest on themselves; it is off until they do. > [!NOTE] > > Client end users are **free** and never count against your license seats, because the customer already paid for the project. Seats count only your own provider-side team accounts. See [Licensing](https://docs.d0pam1ne.blackhatethicalhacking.com/synapse/licensing.md). ## Scoping what a client sees When you add a client, you choose how wide their view is. Three scopes, from broadest to narrowest: * **A project group**: the client sees every project in the group, including ones you add to the group later. This is the way to onboard a customer once and have new projects reach them automatically. * **A whole project**: the client sees all reported issues in that single project. * **Specific issues**: the client sees only the issues you pick, nothing else in the project. Whatever the scope, a client sees an issue only after it is **Reported** (see [How an issue reaches Synapse](https://docs.d0pam1ne.blackhatethicalhacking.com/synapse/overview.md)). Scope controls which reported issues are visible; the Reported gate controls whether an issue is visible at all. ### Project groups Projects can be organized into **groups**, nested folders with a name, a description and members. A project optionally belongs to a group and keeps its own isolated scans, recon and issues. The Projects page offers a **Tree** and a **List** view, a search, and **+ Project** / **+ Group**, with archived projects hidden until you show them. > [!NOTE] > > Group-level client access is the fix for "a new project should reach the client automatically." Invite the client to the **group**, and every project in it, present and future, is in their view. Per-project and per-issue invites still exist for narrower cases. ![A client's projects grouped in the portal](https://mintcdn.com/black-hat-ethical-hacking/OoWrmGEHoSIMtvDf/images/synapse/portal-projects.webp?fit=max\&auto=format\&n=OoWrmGEHoSIMtvDf\&q=85\&s=7b0f91ac05f95cd303d4b44a0d838f03) In the portal, a client's projects are grouped the same way, so a group invite surfaces every project in it as a card. ## Inviting a client **1. Add the client** From **Synapse, Clients**, select **Add a client**, pick their company, and set the scope (group, project, or specific issues). **2. Choose how they get in** Pick one of two ways. **Email a one-time invite link**, and the client chooses their own username and password on it. The link stays valid for 7 or 14 days, 1, 3 or 6 months, a year, or a custom number of days up to ten years. Or **create the account now with a generated password**: you set the username and Synapse makes a strong one-time password. If you add an email, the username and password are sent there automatically; leave it blank and you copy them to pass on yourself. **3. The client sets up** On first sign-in the client sets their own password and turns on two-step login (required), then lands in the portal at `/portal`. This is the same whether they arrived by an invite link or a generated password. ![The branded Synapse client invite email](https://mintcdn.com/black-hat-ethical-hacking/OoWrmGEHoSIMtvDf/images/synapse/client-invite-email.webp?fit=max\&auto=format\&n=OoWrmGEHoSIMtvDf\&q=85\&s=4b80477233bd8266de37c7cc2bf40014) The branded invite: a one-time link that expires, with the first steps the client follows to open their portal. > [!NOTE] > > If a client never received their email or lost it, use **New password** on their row for a fresh one-time password (emailed to them when they have an address, otherwise shown once to copy), or **Resend welcome** to email a link they choose their own password on. **New password** signs out their old sessions at once; either way the client sets their own password again on the next sign-in. > [!NOTE] > > A generated password is a strong one-time password, shown to you once, so copy it before you close the dialog. The client must change it on first sign-in, so it is never stored in the clear and is only ever a way in, not their lasting password. > [!NOTE] > > A client account is sandboxed on the server to the portal and refused everywhere else, so a client can never reach the D0pam1ne console even by guessing a URL. See [The client portal](https://docs.d0pam1ne.blackhatethicalhacking.com/synapse/portal.md). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.