> ## Documentation Index > Fetch the complete documentation index at: https://docs.aireadyscore.com.au/llms.txt > Use this file to discover all available pages before exploring further. # Partnerships > How an advisor and a client connect: who starts it, the states each side sees, consent, permissions, and how it ends. A **partnership** is the consented link between an advisor organisation and a client organisation. It's the only way an advisor gains access to a client, and it always requires the client's agreement, there is never a shared login. ## Who starts a partnership Either side can start it: * **The advisor** sends a connection request from **Create New Client**. Because the client hasn't agreed yet, the advisor sees only the client's **domain**, not its name. The button is **Send connection request**, and the advisor is reminded: *"They approve it and confirm what you can access; a real, consented engagement."* On success: **Request sent to \[domain]**, *"It requires their approval. You'll get no access until an owner or admin there accepts; you can re-request if it's declined or expires."* The request expires after a set period if no one acts on it. * **The client** adds an advisor from **Organisation → Advisors** using **Add advisor**. Only owners and admins can do this. It is a **domain search**, the mirror of how an advisor adds a client: type the firm's **website or email domain** (a pasted email address works too, we use the domain part) and **Search**. A firm already on the platform can be invited straight away; one that isn't reads *"Not on the platform yet. Ask your advisor to get in touch with us to join."*, and a public email provider is refused with *"That is a public email provider, not an advisor firm's own domain."* The invitation can carry an optional **Message to the advisor** (what you would like help with, and anything they should know), which the firm reads while deciding whether to accept. ## What each side sees The two sides use different words for the same relationship. | Situation | The advisor sees | The client sees | | ------------------------------------- | ---------------------- | ------------------------------------------------------------- | | Request sent, awaiting the other side | **Connection Pending** | **Invited**, *"They'll appear as Invited until they accept."* | | Active engagement | **Connected-Active** | **Active** | | Ended (revoked) | **Connected-Ended** | **Revoked** | | Request expired without a response | **Expired** | Not shown | A client may also see a **Needs review** chip when advisor permissions need re-confirming, and the client's Advisors table shows **Invited by**, the person who set the partnership up. While your request is pending, your own Clients page offers **Cancel request** on that row, cancelling withdraws the request without anything reaching the client's team beyond the withdrawn invite. ## Accepting or declining Whoever receives the request approves it with **Accept** or turns it down with **Decline**: * When an **advisor** accepts a client's invitation, they see **Client added.**; declining shows **Invite declined.** * When a **client** accepts an advisor's request, they see *"\[advisor] can now advise your organisation."*; declining shows **Request declined.** ## What an advisor is allowed to do When a client accepts, they also confirm what the advisor may do. There are two levels of access: | Access | What it allows | | --------------------------- | ----------------------------------------------------------- | | **Read-only access** | *"Can view the client's profile, evaluations and reports."* | | **Evaluation write access** | *"Can also run and edit the client's evaluations."* | An advisor with read-only access can look but not act; only **Evaluation write access** lets an advisor start, answer, and submit runs for the client. See [Workspaces](/advisors/workspaces) for the full breakdown of what an advisor can and can't do inside a client. ## Ending a partnership Either side can end it, and both routes are permanent (though you can reconnect later). * **The advisor** uses **End engagement**. The dialog asks **End engagement with \[client]?**, *"This ends your advisory relationship and removes your access to this client's evaluations. This can't be undone, but they can invite you again later."* After it ends, the row shows **Connected-Ended** and is hidden unless you turn on **Show ended**. * **The client** uses **Revoke access** (or **Cancel invitation** if the request is still pending). Revoking says *"This ends the engagement and removes their access to your organisation's evaluations. This can't be undone, but you can invite them again later."* Revoked rows are hidden unless you turn on **Show revoked**. ## Related Your client portfolio and how you switch between clients. Private working copies and what you can do inside a client.