Skip to main content
Audience: MSP staff configuring the portal. Company users have a narrower set of account and company controls; this directory does not grant them access to MSP settings. Open Settings at the bottom of the sidebar. The nested settings navigation shows areas available to your role and enabled features. The settings landing page opens User Settings. A missing section can reflect permissions or feature availability, rather than missing configuration.

​
Choose a settings area

For an initial rollout, use the MSP setup playbook and Launch Center to coordinate the required work.

​
Know when a change saves

There is no universal autosave rule across Settings. Tenant form fields use Save Settings; branding has separate upload and color actions. Editors such as Note Templates save in their dialogs. Other controls, including email defaults or receiving activation, persist immediately. Imports and provider connection actions have their own explicit execution and result. Read the relevant guide before a bulk action. Table filters may narrow what you see without limiting a tenant-wide cleanup or default change. Inspect selected records and the action’s stated scope, then wait for its result.

​
Check the result

Reopen the setting to confirm its saved value, then check the affected feature with the intended role and company. Saving a template does not prove delivery; configuring a role does not prove every client workflow works. If an operation partially succeeds, inspect current values before repeating it.

​
Troubleshooting

If Settings opens but an area is absent, ask an administrator to review the relevant read/write/manage permission and feature availability. If a save fails, preserve the error, reopen the current state and retry only the incomplete work. If a user sees unexpected content, check company scope, role and that content’s visibility settings together.

​
FAQs

No. Header forms, editors, immediate controls and provider actions have different save boundaries. Follow the specific guide.
No. Review the action’s scope and selected records; some operations affect tenant-wide configuration.
Navigation depends on permissions and enabled features. Compare the relevant role and feature access.
No. Review the saved value and test the affected workflow with the intended Company role and scope.