Britixo CRMBritixo CRMEnterprise Help Centre
Ctrl K
Setup, access, permissions and lifecycle

Understand when clients see Client Briefs

The client menu is shown only to a signed-in client whose customer account has explicitly linked discovery requests. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.

Audience: CRM administrators, project teams, developers, authorised client contacts and public prospectsPermission: Authenticated linked client contactModule v1.1.1
Jump to steps
Where to goClients Area → Client Briefs
Before you start
  • Verify the module is active and use the exact navigation shown above.
  • Use an account with the stated module and core CRM permissions.
  • Use known test records when changing statuses, visibility, saved filters or global navigation.

What you’ll accomplish

The client menu is shown only to a signed-in client whose customer account has explicitly linked discovery requests. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.

Follow these steps

  1. Go to Clients Area → Client Briefs.
  2. Find the record, endpoint, field or action used to understand when clients see client briefs.
  3. Complete the displayed values exactly as described in this guide.
  4. Select the available save, submit, send, upload, create, update or confirm action.
  5. Return to the related register, portal, activity log or API response and verify the expected result.

Fields and options to review

Workspace or endpointClients Area → Client Briefs
PurposeThe client menu is shown only to a signed-in client whose customer account has explicitly linked discovery requests.

Rules the system enforces

  • The action is available only where the supplied module exposes it and the signed-in user or API client meets the stated access conditions.
  • Internal helpers are documented under the visible workflow or endpoint they support rather than presented as invented menu pages.

How to confirm it worked

  • The understand when clients see client briefs workflow completes without a validation, permission, ownership or availability error.
  • The related record, portal view, activity entry, notification log or API response shows the expected state.
  • Client-visible, public and API data remains limited to the code-backed ownership and visibility rules.

Security, privacy and operational checks

  • Use controlled test records and non-production credentials before wider rollout.
  • Grant least privilege and protect secure links, personal data, uploaded files, signatures, API tokens, allowed origins and server IPs.
Open the staff menuUnderstand the customer profile tabSetup, access, permissions and lifecycleBrowse all Client Discovery & Project Briefing Portal guidesClient portal overviewAdd and manage customer contactsConfigure customer contact permissionsUpload and share customer filesConfigure SMTP email deliveryReview email delivery issues