Can my invited colleagues see all the sidebar menus or only what I allow?
Invited users only see the sidebar modules you have explicitly granted them access to. They do NOT get full access by default — you control exactly what they can view and use.
How it works
When you invite a team member via Settings → Users → Invite User, you select which modules they can access using the "Module Permissions" checkboxes. Each checked module becomes a visible sidebar item for that user. Unchecked modules are completely hidden from their sidebar and inaccessible even if they try to navigate directly to the URL.
The chat assistant follows the same permissions for Buildings, Tenants, Invoices, Cost Allocation, Reports and Tenant Hub: it will not show or change anything in one of those modules for a user who cannot open it, and says so instead.
The 9 modules you can grant or revoke
- Buildings — view and manage building details
- Tenants — view and manage tenants/lessees
- Tenant Billing — create and manage tenant bills
- Invoices — view and manage utility invoices
- Invoice Reader — upload and process PDF invoices
- Cost Allocation — configure cost distribution rules
- Reports — view and generate reports
- Analytics — access energy, water, gas, and waste dashboards
- Tenant Hub — communicate with tenants and manage issues
What invited users always see (regardless of permissions)
- Dashboard (home page) — always visible
- My Account — where they manage their own profile and security settings
What invited users never see
- Settings — only the account owner (admin) can access Settings, which includes user management, billing, extensions, and localization
Example: If you want a colleague to only handle invoices and reports, check only "Invoices", "Invoice Reader", and "Reports" when inviting them. Their sidebar will show Dashboard, Invoices, Invoice Reader, Reports, and My Account — nothing else.
Changing permissions later: Go to Settings → Users → find the user → click the key icon → toggle modules on or off → Save Permissions. Changes take effect on the user's next page load.