This page covers the administrative surface of Ocular — adding teammates, controlling what they can see, and configuring display preferences. Most of these settings live under Settings in the left navigation.Documentation Index
Fetch the complete documentation index at: https://docs.ocular.dev/llms.txt
Use this file to discover all available pages before exploring further.
Users
Invite teammates, assign roles, suspend, or remove.
Groups
Scope access by team, project, or channel.
Display preferences
Number format, currency, fiscal calendar, time zone.
Users [#users]
Invite a user
Fill in details
Enter the email address, assign a role, and optionally add the user to one or more groups.
Roles
Roles control what a user can do across the workspace. The same role applies everywhere the user has access — group membership is what scopes where the role applies.Viewer
Can view: dashboards and reports they have access to.Cannot edit or administer.
Analyst
Can view: everything Viewer can.Can edit: saved charts, dashboards (own and shared), Chart Builder, configuration sheet.
Admin
Can view + edit: everything Analyst can, plus data sources, channel mapping, COGS, targets, fees.Can administer: users, groups, billing.
Owner
Can do everything Admin can, plus brand deletion and ownership transfer.
Edit, suspend, or remove a user
Edit a user's role or group membership
Edit a user's role or group membership
Settings → Users & Groups → click the user → update role or groups → Save.
Suspend a user
Suspend a user
Settings → Users & Groups → click the user → Suspend. Their access is revoked but their saved charts, comments, and history are preserved. You can reactivate later.
Remove a user permanently
Remove a user permanently
Settings → Users & Groups → click the user → Remove. Their saved charts and dashboards remain (orphaned to the workspace), but their account is deleted and they receive a notification.
Groups [#groups]
Groups streamline access control by letting you assign permissions to many users at once. Instead of granting access source-by-source to each new hire, you put them into the right group and they inherit the group’s access.Create a group
Why use groups
Onboarding new hires
Drop them into “Marketing Team” and they immediately have the right access.
Cross-functional projects
Create a group for the project, scope its access, dissolve when done.
Channel-specific teams
Scope a group to a particular channel (e.g. quick commerce vs. DTC).
Common group patterns
Leadership
Access: All brands, all dashboards, P&LRole: Viewer
Marketing team
Access: Marketing report, Ad & Campaign Performance, Creative Deep DiveRole: Analyst
Data team
Access: Everything, plus Chart Builder write accessRole: Admin
Agency / external
Access: Specific dashboards only, no raw data exportRole: Viewer
Finance
Access: P&L, Sales Performance, CohortsRole: Viewer or Analyst
Brand and display preferences [#display-preferences]
Per-brand display settings live in Settings → Display Preferences.Number format
Lakhs/crores vs. millions/billions.Default: Lakhs/crores (India).
Currency
The currency shown in all financial views.Default: Brand’s primary market currency.
Financial year start month
Aligns YTD/quarterly/annual rollups to your fiscal calendar.Default: April (India).
Time zone
The time zone shown in charts (data is always stored in UTC).Default: Brand’s primary market timezone.
Week start
Sunday or Monday.Default: Monday.
Date format
DD-MM-YYYY, MM-DD-YYYY, YYYY-MM-DD.Default: Locale-based.
Workspace export
You can export your Ocular data and configuration at any time.Data exports
Every report, dashboard, and Chart Builder view supports a CSV export from its three-dot menu.
Configuration exports
Settings → Workspace → Export Configuration — full JSON of channel mapping, COGS, targets, custom costs, dashboards, saved charts. Re-importable into a fresh brand.
Your source data always remains in the source systems you connected. Ocular reads from them; it is not the system of record for your orders, customers, or ad spend. Disconnecting Ocular does not affect anything in Shopify, Meta, Blinkit, or any other connected source.
Where to go next
Working with the Ocular team
If you hit a permissions edge case this page does not cover.
Implementation checklist
Sequencing for new workspace rollouts.
Connect Your Data
Once users and permissions are set, get the connectors running.
