Use this guide when a client asks where to find something in Portal. Portal shows the work your agency has shared with their organization.
Your agency owns and controls the Portal. A client’s Owner or Admin role delegates access within a client relationship. Neither role transfers Portal ownership.
What a client can find
- Projects and the milestones you have shared.
- Shared files and project updates.
- File-review actions for eligible people using legacy company-membership access. Configured relationship grants alone do not currently enable file-review decisions.
- An Inbox for messages and requests.
- A People page with the admitted client relationships. An Owner can review admitted people and assign another Member as Owner within the selected relationship. An admitted Admin or Owner can invite a new Member and edit eligible active Members’ direct grants within that relationship’s Project limits. The agency can undo those edits. Legacy company access has a separate company roster.
In the legacy company-membership model, company membership provides access to company-shared work. Separately configured relationship access can restrict a person’s projects. Sharing and private-conversation audiences still apply, so another person’s access does not establish what this client can see. See Client roles and the People page for legacy company roles.
If something is missing, check both the client’s Portal Settings and the sharing setting on the project or file. Turning on a Portal section does not share every item inside it.
A client sees their own organization’s name in Portal, even if your agency uses another name in Studio. See Edit a client’s details to check that name.
Requests
After accepting a configured relationship invitation, a client can submit a Request before any Engagement or Project exists. The form uses Client relationship to keep the Request in the intended relationship. A sole relationship is selected automatically; the client chooses when several are available.
Engagement (optional) and Project (optional) let the client identify existing work. To choose an existing Project in this form, select its Engagement first. Project choices include only currently shared work within their scope. Changing the relationship clears both selections; changing the Engagement clears the Project. An empty Project selection does not prevent a Request.
Your agency receives the Request and handles turning it into work. You can accept it without creating work, then select a real Engagement when tracked work is needed. Starting or converting a Request does not grant access to excluded Projects or private conversations. Legacy company-membership access keeps its existing Engagement-bound intake.
For access and sharing steps, see Manage portal access and Share work with clients.