Understand access and privacy

Work in the correct account #

Organisation records belong to that organisation’s workspace. Individual records belong to the individual account. Being able to switch perspectives does not combine their permissions. If a record is missing, first confirm the account mode and organisation before assuming it was deleted.

A role controls which operations you can perform. Viewing a team or check does not necessarily allow editing it, inviting colleagues or managing billing. Hidden or disabled controls can reflect access, record state or pre-launch availability.

Share access through the product #

Invite colleagues through Members using their own accounts and the least access needed. Do not share passwords, one-time codes, identity files or private signing links in a team chat. A tutorial URL is public reference material; a check or contract URL still requires the recipient’s own authorisation.

For a contract, access to the document and authority to sign it are separate. A workspace member may be able to read an agreement but not sign for a named recipient. Use the displayed parties and signing status to identify the responsible person.

Keep sensitive information out of chat #

Ask about workflow steps without pasting identity document images, document numbers, dates of birth or raw applicant evidence. Use the check’s permitted summary and dedicated evidence screen. Chat history is not a replacement for the evidence store or formal audit trail.

Assistant messages and proposal details are stored encrypted at rest by the workspace. Encryption does not make it appropriate to collect unnecessary applicant information. Access and retention controls still apply.

Resolve an access problem #

1. Check that you are signed into the intended account.
2. Confirm your invitation has been accepted and membership is active.
3. Open the workspace directly rather than an old bookmarked action URL.
4. Ask an authorised administrator to review your role if a required control is unavailable.
5. Use Support if the workspace availability message prevents entry.

Do not repeatedly change identifiers in URLs to find a record. The application must continue to enforce ownership and permissions regardless of how a link was obtained.

Detailed walkthrough #

1. Separate access from consent

Your personal profile identifies your account; access to organisation work is determined separately by membership and role. Consent recorded for an application has its own purpose. Do not treat changing a profile preference as changing all historic application permissions.

2. Review sensitive account actions

Read the privacy and security information available to your account before using a sensitive control. Export, disconnect and deletion actions have separate effects and may require confirmation. This walkthrough does not perform those actions or remove evidence.

3. Ask about the right record

For a privacy question, identify whether it concerns your personal account or a particular application. Provide the appropriate reference through the support channel, without attaching identity documents or passwords. This helps locate the request without exposing unnecessary information.

Practise this section #

Open Help & tutorials, select this guide and choose Start practice walkthrough. Read each highlighted component before continuing. Use Back to revisit an explanation and Retry if a sample has not loaded. The walkthrough uses fictional records; do not enter real applicant information.

Use Exit tutorial to leave and keep your place, then Resume walkthrough in this guide to continue. When returning from practice to a real workspace, review the actual record and your permissions before making a change. Tutorial completion does not perform the underlying task.

Before using this guide #

Open your personal account for privacy choices, or Users for organisation access. Decide which record and purpose your request concerns.

Worked example #

Removing someone from a team may leave their organisation membership active. Use the member-access workflow when the intention is to revoke workspace access.

Guided component walkthrough #

Each component has one short guided step. Read the explanation, then choose Next; Back revisits the previous component. The cursor only demonstrates useful navigation or an explicit action. Replay action repeats that demonstration, and Skip animation keeps the explanation. Use this written guide for feature details.

Your account menu

• Your account menu: The account menu is the way to anything that belongs to you rather than to the workspace. The pointer opens it for you.

My account

• My account: This entry opens your own profile. The pointer selects it for you.

Your profile

• Your profile: Sign-in details and personal information sit here, separate from organisation membership and from any real account.

Separate access from consent

• Separate access from consent: Your personal profile identifies your account; access to organisation work is determined separately by membership and role. Consent recorded for an application has its own purpose. Do not treat changing a profile preference as changing all historic application permissions.
• Data request context: Use Your data to understand the account-level choices available to you. Identify whether your question concerns your account, an application or an organisation record before making a request.
• Review sensitive account actions: Read the privacy and security information available to your account before using a sensitive control. Export, disconnect and deletion actions have separate effects and may require confirmation. This walkthrough does not perform those actions or remove evidence.
• Read before confirming: Sensitive account controls can have consequences beyond this page. Read the stated scope and confirmation carefully in your real account; the cursor only points at this panel.
• Ask about the right record: For a privacy question, identify whether it concerns your personal account or a particular application. Provide the appropriate reference through the support channel, without attaching identity documents or passwords. This helps locate the request without exposing unnecessary information.

Related guides