Agiled Docs

Module settings control which areas of Agiled appear for the workspace. Use them to keep navigation focused on the features your team actually uses.

Module settings are workspace-level. Turning a module off can remove it from the sidebar for everyone, even users whose roles would otherwise allow access.

Use module settings for workspace focus, not as the only security layer. Roles and permissions still decide what users can do inside enabled areas.

Turn Modules On Or Off

Open Settings.
Go to Modules.
Turn modules on or off with the switches.
Select Save changes.

Available modules can include dashboard, CRM, finance, HRM, products, commerce, docs, files, productivity, scheduling, workflows, agents, chat, and reports.

Before disabling a module, check whether active workflows, reports, public links, integrations, or team procedures still depend on it.

Make module changes during a quiet period when possible. Users may need to refresh, and hidden modules can interrupt work if someone is actively using that section.

Important Behavior

At least one module must remain visible. If you hide a module, users may no longer see that section in the sidebar even if they still have permission to use it.

Disabling a module is not the same as deleting its records. It mainly controls workspace visibility and navigation. Re-enable the module if the team needs to return to that area.

Check saved links, workflows, reports, imports, integrations, public pages, and team documentation. If the module owns customer-facing links or automations, pause or update those workflows before hiding it.

Module Dependency Examples

Review common dependencies before changing module visibility:

Finance may depend on Products for line items and Files for attachments.
Scheduling may depend on connected calendars and public booking pages.
Docs may depend on Files, templates, public signing links, and CRM recipients.
Projects may depend on Tasks, Time Tracking, Files, and customer records.
Reports may depend on the source modules they summarize.

If a team still needs the records, reports, or public links from a module, leave it enabled until the replacement process is ready.

If A Page Is Missing

Check these in order:

The module is enabled.
The user has permission for the module.
The workspace plan includes the feature.

After changing modules, ask affected users to refresh the app or sign in again. Then test the sidebar, direct page link, and any connected workflow or public page that depends on the module.

Troubleshooting

If a module is enabled but still hidden, check the user's role and direct permissions.

If a direct link opens but the sidebar item is missing, refresh the app and confirm the module setting saved.

If a public workflow breaks after disabling a module, re-enable the module and review the dependent workflow or public page before trying again.

Roll Out Module Changes

For larger teams, announce module changes before saving them. Include which section will disappear, what users should do instead, and who owns questions.

After saving, ask one user from each affected role to refresh the app and confirm their sidebar, direct links, and daily workflow still behave as expected.

Configure Workspace Modules