Troubleshoot missing client portal sections
Check contact permissions, customer relationship, document status and visibility settings. 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 contact permissions / Record visibility
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
Check contact permissions, customer relationship, document status and visibility settings. 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 the affected area: Customer contact permissions / Record visibility.
- Capture the exact record, user, time, status and message involved; avoid changing multiple settings at once.
- Check user permissions, record assignment and active/inactive status first.
- Verify required configuration such as SMTP, cron, gateway credentials, webhook URL or contact permissions.
- Check activity, email, pipe or gateway logs available in Britixo CRM and the connected service.
- Retest with a controlled record after correcting one identified cause.
- Escalate with the captured evidence if the issue remains; do not expose credentials or personal data in screenshots.
Fields and decisions to review
Company or individual nameCheck 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.
Primary contactCheck 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.
Billing and shipping addressCheck 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.
Country, currency and 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.
Customer groupCheck 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.
Assigned staff and portal 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
- Search for duplicates first.
- Use a shared business email only when appropriate.
- Check contact permissions before sending portal access.
- 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.
Browse connected topics:paymentcheckcurrencyapprovalinvoiceserviceproviderclient portalnotificationsemailcustomers
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.