Allow portal section: Customer files
Authorised customer files.
Exact navigationAdmin Area → Utilities/Tools → API Gateway → Create Client Portal API
Before you begin
- Confirm 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 this guide covers
Authorised customer files. The instructions below follow the supplied module’s live menu, controller, form, model and JavaScript flow.
Exact step-by-step process
- Open Admin Area → Utilities/Tools → API Gateway → Create Client Portal API.
- Locate the record, endpoint, field or action used to allow portal section: customer files.
- Complete the displayed values exactly as described in this guide.
- Select the available save, submit, send, upload, create, update or confirm action.
- Return to the related register, portal, activity log or API response and verify the expected result.
Fields, choices and supported possibilities
Allowed sectionCustomer files
PurposeAuthorised customer files.
Code-backed validations and workflow rules
- The external session can retrieve the section only when the profile includes its key and the client identity owns the related records.
Expected result and verification
- The allow portal section: customer files 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.