Client portal overview
This guide explains the areas a contact can see and how staff permissions differ from contact permissions. 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.
Where to goCustomer-facing portal
Before you startThe screen or action may be hidden when your role lacks permission, the related module is inactive, or a required setting has not been configured. Ask an administrator to review access rather than using another person’s account.
What you’ll accomplish
Understand the areas a contact can see and how staff permissions differ from contact permissions. Britixo CRM keeps the result connected to the relevant customer, staff member and operational history where the feature supports those relationships. That connection is important for search, reporting, client portal visibility and future automation.
Follow these steps
- Go to Customer-facing portal.
- Identify the purpose of the screen and the records visible to your role.
- Use search, filters, status controls and record links to move from summary information to detail.
- Check related customers, ownership, dates, activity and financial information before taking action.
- Follow the linked task-specific articles for creation, configuration, sending, conversion or troubleshooting.
- Verify every completed action through the resulting status, timeline, document or notification.
- Contact an administrator when a menu or action is unavailable rather than attempting to bypass permissions.
Fields and decisions to review
Name and emailCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
RoleCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
DepartmentsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
PermissionsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
LanguageCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Active and authentication settingsCheck this value against the source record before saving. If the field is optional and no verified value is available, leave it blank rather than entering placeholder data.
Checks before you finish
- Apply least-privilege access.
- Use a unique email account.
- Reassign work before deactivation.
- Check whether the result should be visible to a customer contact or only to staff.
- Confirm the final status, activity entry, generated document or notification before leaving the record.
Permission and data safetyDeletion, refunds, signature clearing, module changes, payment configuration and privacy actions can affect linked records or legal history. Use the least destructive action available and follow your organisation’s approval process.
Continue with related guidance
Connected discovery, service and API guides
Was this guide useful?Your response is stored only in this browser.