Every screen, explained next to the real thing
Each lesson opens the actual page of RAYA OS beside its explanation — the same interface you will use, filled with sample data. Read a step, press “Show me”, and try it right there.
- 12 chapters
- 51 lessons
- Live interface, no screenshots
The live screens run in a shared demo workspace. Its data is sample data, visible to every visitor and reset every day — please don’t type anything real into it.
What you will learn
Read in order, or jump straight to the part you need.
- Chapter 1
Getting started
How the workspace is laid out and where everything lives.
3 lessons - Chapter 2
Your day
Plan, focus and close the day with the planner, calendar and daily check-in.
6 lessons - Chapter 3
Work & projects
Tasks, projects, incoming requests and approvals — the team’s shared work.
4 lessons - Chapter 4
RAYA AI — AI assistant
Ask about your company’s data and let the assistant draft the work.
2 lessons - Chapter 5
Documents & knowledge
Write, share and find the company’s documents and the facts inside them.
3 lessons - Chapter 6
Communication
Team channels and shared mailboxes, next to the work they are about.
3 lessons - Chapter 7
Customers & sales
From the first lead to the signed deal, the proposal and the support that follows.
10 lessons - Chapter 8
People & HR
People records, attendance, leave, shifts, timesheets and training.
8 lessons - Chapter 9
Automation
Let routine steps run themselves when something happens in the workspace.
2 lessons - Chapter 10
Finance
Invoices, payments, parties and the accounts behind them.
6 lessons - Chapter 11
Servers & integrations
Keep the company’s servers and connected services in the same workspace.
2 lessons - Chapter 12
Workspace settings
Members, roles, modules, language and regional formats.
2 lessons
Getting started
RAYA OS is one workspace for the whole company: tasks, customers, conversations, documents, people, finance and automation share the same records, so nothing has to be copied from one tool to another.
Start here: learn the frame that surrounds every page — the sidebar, search, notifications and the assistant — then the home screen that tells you what needs you today.
/dashboardGetting around RAYA OS
Welcome to RAYA OS
This short tour shows you the parts of the screen that never change: how to move between modules, where the page tools live, and how to get help again later. It takes about a minute, and you can leave at any point.
The module rail
Every module the workspace has enabled for you appears here. Items you cannot see are either not part of your plan or not open to your role — nothing is hidden at random.
Groups and pinning
Modules are grouped by the kind of work they serve. Open and close a group to keep the rail short, and pin the pages you open every day to the top so you stop hunting for them.
Your workspace
Everything you see — tasks, deals, documents, people — belongs to the workspace named here. If you are a member of more than one, switch from this menu; data never mixes between them.
The page header
The header always names the page you are on and carries its main buttons. On a detail page it also shows the record you opened, so you can tell at a glance what any action will apply to.
The ? beside the title
This is how you get a tour of any page. Press it and the guide walks through that page section by section. It is always there, so nothing you learn here has to be remembered.
Filters and views
Most list pages keep their search, filters and view switch in one row under the header. Filters stay in the address bar, so a filtered list can be bookmarked or sent to a colleague as a link.
Search and the command palette
One box searches across the workspace and also runs commands — jump to a page, open a record, start something new. Press Ctrl+K (⌘K on a Mac) from anywhere instead of reaching for the mouse.
Notifications
Anything assigned to you, mentioning you, or waiting on your approval lands here. The same alerts can follow you to the browser and to Telegram or Bale — you choose which in settings.
The assistant
Ask about your own data in plain language — what is overdue, which deal moved, what a document says. When it proposes a change it shows you exactly what it will do and waits for your approval.
Theme, language and account
Light or dark, the interface language, your profile and sign-out all live in this menu. Changing the language switches the whole product, including this guide.
That is the frame
From here on, every page explains itself: press the ? beside its title for a tour, or the small i beside any section title for a one-paragraph explanation of that section alone.
/dashboardHome
The workspace at a glance
Home answers one question: what needs me today. Every card links straight to the module it summarises.
Your own numbers
The top row counts only work that is yours — assigned to you or waiting on you, not the whole workspace.
Shortcuts and suggestions
Quick actions start the things you do most often; the suggestion beside them points at one thing worth looking at today.
Your work, first
The main column gathers what is assigned to you across every module, one card per source, so you never have to go looking.
Things that need attention
The side column is the exceptions: overdue work, stalled deals, failed jobs — the items that will not resolve themselves.
/notificationsNotifications
Everything that wants you
Assignments, mentions, approvals and system alerts, newest first.
Filter to the ones that act
Separate what needs a decision from what is only informing you.
Reading is not doing
Marking read only clears the badge; the task or approval behind it still waits in its own module.
Where alerts follow you
The same notifications can be delivered to the browser and to Telegram or Bale once you link an account.
Your day
The planner is private: it pulls your assigned tasks, your own notes and your calendar into a single plan that only you see. Nothing you rearrange there changes the team’s boards.
A good day here has three moments: pick a few priorities in the morning, work through them in focus, and close the day with a short review and check-in so tomorrow starts where today stopped.
/plannerPersonal planner
Your day, not the team’s
The planner is private. It gathers your work tasks, your own notes and your calendar into one plan that only you see.
Views of the same work
Today, Inbox, Board, Backlog, Timeline and Grid are different windows onto the same records — switching a view never moves or changes anything.
Plan the day
The morning plan asks you to pick a few priorities and keep a buffer. The capacity line warns you when the day is already full.
Write it down first
Quick add understands ordinary sentences — “lunch with Sara tomorrow at 1 for 45 min”. It lands in your inbox; decide where it belongs later.
Goals give tasks a reason
Attach tasks to a goal and the planner can show progress toward something larger than a single day.
Routines repeat themselves
Anything you do on a rhythm becomes a routine, so it reappears on the right day without being retyped.
Close the day
Review shows what you finished and what did not happen, and moves the leftovers forward in one step.
/planner/goalsGoals
Something to aim at
A goal is an outcome you are working toward, with the tasks that move it attached underneath.
Create a goal
Give it a name and a horizon. Keep it small enough that finishing it is imaginable.
Progress is counted, not claimed
The bar follows the tasks linked to the goal, so it only moves when real work closes.
/planner/routinesRoutines
Habits, not reminders
A routine reappears on its own schedule; you never re-create it.
Set the rhythm
Choose how often it repeats and which days it may land on; the planner does the rest.
Missing one is fine
A skipped occurrence does not delete the routine — the next one still arrives on time.
/planner/reviewReview and insights
What actually happened
A short account of the period: finished, missed, and where the time went.
Look for the pattern
One bad day means little; the same slip three weeks running is worth changing something for.
Move the rest forward
Anything left open can be carried to the next period in one action instead of one by one.
/calendarCalendar
Time you have committed
Meetings, class sessions and scheduled work in one place, in your own calendar system and locale.
Day, week, month
Switch range to change the question: what is next, how full is the week, when is that month busy.
Create an event
New entries can be linked to a lead, a project or a class, so the record keeps its own history.
Where entries come from
Items created in other modules appear here automatically; the source is shown on each one.
/daily-reportsDaily check-in
A short note about your day
What you worked on, what blocked you, what is next — written once a day, read by your manager.
By person or by day
A manager reads one day across the team; you read your own across weeks.
Write today’s
Three honest lines beat a paragraph written to look busy.
Blockers are the point
The section that gets acted on is the one where you say what is stopping you.
Reminders, and the optional summary
A reminder can nudge you at the end of the day, and an AI summary can be turned on — the check-in works perfectly well without it.
Work & projects
Every piece of work is a task with an owner, a status and a due date. A task can belong to a project, link to a customer or a deal, and carry the comments, files and results of everyone who worked on it.
Projects group tasks into milestones and budgets; the requests inbox catches work that arrives from outside; approvals collect every decision that is waiting on you in one list.
/tasksTasks
Operational work
Every task the team is tracking. Unlike the planner, this is shared: what you change here, colleagues see.
List, board, or grid
The view changes how the same tasks are drawn, never which tasks exist.
Filters live in the link
Assignee, status, priority and project all go into the address, so a filtered list can be shared as a URL.
Create a task
The form carries every field a task can have; only a title is required, the rest can wait.
Opening a task
A task carries its own description, checklist, attachments, comments and full history of changes.
Keep one open while you work
Docking a task keeps it beside you as you move around the app, so you do not lose your place.
/projectsProjects
Work with a shape
A project groups tasks, people, milestones and a budget into something with a beginning and an end.
Narrow the portfolio
Filter by status, owner or client to answer a specific question instead of scanning everything.
Start a project
Name it and give it an owner; workstreams, milestones and members can be added as the work becomes clear.
Health is calculated
Progress and risk come from the tasks and milestones underneath, not from a status somebody typed.
/inboxRequests
Internal forms
Structured asks between colleagues — access, purchases, changes — instead of a message that gets lost.
Mine or everyone’s
Switch between what you asked for and what has been asked of you.
Raise a request
Pick the template that matches; its fields exist so the person answering has what they need.
A request needs an owner
Unassigned requests are the ones that quietly expire; assigning one starts the clock.
/approvalsApprovals
Decisions waiting on someone
Everything across the workspace that cannot proceed until a person says yes or no.
Waiting on me
The default is your own queue; widen it only to see where a request is stuck.
A decision is not reversible by default
Approving usually triggers the next step immediately, so read the request rather than the title.
Hand it on rather than sit on it
If a request is not yours to decide, reassigning it is faster than everyone waiting for you to notice.
RAYA AI — AI assistant
RAYA AI reads the same records you can read — tasks, customers, documents, mail — and answers with links back to them. It never sees more than your role allows.
When it suggests a change — a new task, an updated deal — it only proposes it; nothing is written until you confirm. Admins decide where data may be processed and which actions need approval.
/aiAssistant
Ask about your own data
The assistant reads what you are allowed to read and nothing else — it can never show you a record your role hides.
Ask in your own words
Plain questions work best: what is overdue this week, which deals stalled, what did we agree in that meeting.
It says where it looked
Answers cite the records they came from, so you can open the source instead of trusting a summary.
Changes need your approval
When the assistant proposes to create or edit something, it shows the exact change and waits — nothing is written until you confirm.
Conversations are kept
Earlier threads stay available, and the same conversation follows you into the side panel elsewhere in the app.
/settings/ai-governanceAI governance
What the assistant may do here
Workspace-level limits on top of whatever the platform already allows.
Where content comes from matters
Text the assistant reads from records is treated as data, never as instructions it should follow.
Write actions are gated
Turning writes off leaves the assistant fully useful for questions; nothing it reads is affected.
Every proposal is recorded
Approved or not, a proposed change leaves a row you can review afterwards.
Documents & knowledge
Documents hold policies, templates, contracts and forms, each with its own visibility. Fillable templates turn into finished documents without retyping.
The knowledge graph links people, customers, projects and documents to one another, so search and the assistant can answer questions that span several modules.
/documentsDocuments
Written things, kept
Policies, notes, contracts and fillable templates — everything the workspace needs in writing.
Filters, not folders
There is no folder tree to maintain; type, owner and tag in the header do the same job without going stale.
Create or upload
Write a document in place, or bring in a file that already exists.
Flat, or as a hierarchy
The tree view groups by relationship for the moments when structure genuinely helps.
Sharing is explicit
A document is private to its owner until it is shared with a person, a team or the whole workspace.
/knowledgeKnowledge
What the workspace knows
Facts drawn from your own records — people, accounts, projects, documents — and the links between them.
Search by meaning
Ask for a thing rather than a keyword; results are entities, not documents that happen to contain a word.
Entities
A person, company, product or place the workspace has come to recognise across several sources.
Every fact carries evidence
A relation is only stored when a source supports it, and the supporting record is always one click away.
/knowledge/sourcesKnowledge sources
Where the facts come from
Each source is one module or integration the graph is allowed to read.
State at a glance
Filter to sources that are off, stale or failing rather than reading the whole list.
Sync, rebuild, drift check
Sync fetches what changed, rebuild starts over, and a drift check compares the graph against the source.
A source without a permission check stays off
The graph refuses to index anything it cannot filter by the reader’s permissions.
Communication
Discussions are the team’s channels and direct messages; a message can mention a person, link a task or become one. Channels can also publish posts, like a company feed.
Mail connects your existing mailboxes. Shared accounts, templates and per-account access let a team answer customers from one place without sharing passwords.
/discussionsDiscussions
Conversation with a home
Channels and direct messages inside the workspace, searchable long after the moment has passed.
Channels
A channel gathers everyone working on one subject; some are announcement feeds where posts come from the channel itself.
Mention to involve
Naming someone notifies them; attachments and links to tasks or documents keep the context with the message.
Reply in a thread
Threads keep a side conversation from burying the main channel.
Who can see it
Membership decides visibility; adding somebody later does not retroactively hide what they can now read.
/mailCompany mail, inside the workspace
Read and send from the accounts your workspace has connected, with the record they belong to alongside.
Search and filter
Narrow by folder, account, unread state or attachment before scrolling.
Compose
Pick which connected identity sends the message; the recipient sees that address, not yours.
Folders come from the server
They mirror the real mailbox, so moving a message here moves it in every other mail client too.
Link a message to a record
Attaching a message to a lead or deal puts it in that record’s timeline for everyone who works on it.
/mail/templatesMail templates
Write it once
Messages you send often, kept ready so the wording stays consistent across the team.
Create a template
Give it a clear name — colleagues will pick it from a list without opening it first.
Placeholders fill themselves
Fields such as the recipient’s name are substituted when the message is composed, not when it is saved.
Customers & sales
A lead is someone who might buy. Once qualified it becomes a deal that moves through your pipeline stages; companies and people are kept as accounts and contacts, and a company that has won a deal is shown as a client.
Calls, meetings and notes are logged as activities on the record they belong to. Proposals price the deal, the support inbox tracks every request against its SLA, and reports show where the pipeline stands.
/crm/workspaceSales workspace
Your day in sales
One screen that answers what to work on next, instead of five lists to check in turn.
The call queue
Leads sorted by what is due, not by when they arrived.
Targets
Your number for the period and how much of it is already committed.
Nothing falls through
Every promise you made to call back appears here on the day you promised it.
/crmLeads
People who might buy
A lead is an unqualified opportunity. It becomes a deal when there is something concrete to sell.
Find your slice
Owner, stage, source and date filters answer most questions without a report.
Add a lead
Name and a way to reach them is enough; the rest is filled in as you learn it.
Stages are shared
Everyone sees the same stage names, which is what makes the pipeline report mean anything.
Open a lead
Calls, emails, meetings and notes all collect on one timeline, whoever recorded them.
/crm/dealsDeals
Money with a date on it
A deal is a specific amount you expect to close by a specific time.
Slice the pipeline
Filter by stage, owner, close date or value to see only the deals your question is about.
Create a deal
Attach it to an account so the customer’s history stays in one place.
Moving a stage is a claim
Advance a deal only when something real happened; the forecast is only as honest as the stages.
Forecast is arithmetic
Expected value comes from amount and stage; nobody types a forecast number by hand.
/crm/accountsAccounts and clients
The organisations you sell to
An account is a company; contacts are the people inside it and deals are what you sold them.
Clients versus prospects
Filter to see only the accounts that have actually bought something.
Add an account
Create the company first, then attach its people and its deals to it.
“Client” is earned, not ticked
An account counts as a client because it has a won deal — there is no checkbox to set by hand.
Totals come from the deals
Revenue and deal counts on an account are recalculated, so they can never disagree with the deal list.
/crm/contactsContacts
The people, not the companies
Individuals you deal with, each usually attached to an account.
Filter by status or account
Useful when you need every decision-maker at one company, or everyone at a given stage.
Add a contact
Link them to their company so their emails and meetings land on the right account timeline.
Status is your own list
Contact statuses are a catalogue your workspace maintains, so you can name the stages the way your team talks.
/crm/meetingsMeetings
Time booked with a customer
Scheduled conversations, with the lead or deal they concern attached.
Upcoming or past
Past meetings without a recorded outcome are the ones worth revisiting.
Schedule a meeting
It appears in the calendar as well, so it competes for time with everything else you committed to.
Record what came of it
A meeting with no outcome teaches the pipeline nothing and has to be asked about again.
/proposalsProposals
What you promised, in writing
Every offer sent to a customer, with its status and the deal it belongs to.
Waiting on whom
Filter to proposals waiting on the customer versus those waiting on you.
Draft a proposal
Start from the deal so the amounts and the customer are already right.
Approval before it leaves
Proposals above a threshold go through approvals; the request appears in the approver’s queue automatically.
/supportSupport
Customers asking for help
Tickets raised by customers or by your team on their behalf.
Sort by urgency
Priority and age together tell you what is genuinely at risk.
Open a ticket
Record the customer’s own words before summarising them; details get lost in paraphrase.
Response clocks
The clock runs from when the customer last wrote, not from when you last looked.
/crm/reportsCRM reports
Questions about the pipeline
Numbers built from the same records you edit every day — no separate data entry.
Choose the period
Comparisons are only meaningful when both sides cover the same length of time.
Read conversion, not volume
The stage where most deals stop is more useful than the total number of leads.
Take it with you
Export produces the rows behind the chart, so the numbers can be checked outside the product.
/crm/formsLead capture forms
A public front door
Published forms create leads directly from your website, with no login for the visitor.
Build a form
Ask for as little as you can; every extra field costs you submissions.
Fields map to lead fields
What a visitor types goes straight into the lead record, so name them the way the CRM does.
Publishing makes it public
The link works for anyone who has it; unpublish to close the door without deleting what came in.
People & HR
Workforce keeps one record per person — role, team, contract and manager — and builds everything else on it: who is in today, who is on leave, who covers which shift.
Requests such as leave or attendance corrections go to the right manager for approval, and reports turn the month’s attendance and timesheets into something payroll can use.
/workforceWorkforce
People operations
Who works here, when they work, what they are owed and how they are doing.
Pick a period
Almost everything in this module is a question about a specific week or month.
Sections, not separate products
Attendance, leave, shifts, timesheets and performance all read the same people records.
What needs a decision today
Pending leave, unapproved timesheets and uncovered shifts surface first because they expire.
/workforce/peoplePeople
The employee record
One row per person, holding the details every other section reads.
Filter by team or status
Active, on leave and departed people are all kept; the filter decides which you see.
Add a person
An employee record is separate from a login; someone can exist here without a user account.
History stays with the person
Contracts, leave balances and reviews accumulate on the record rather than in separate files.
/workforce/attendanceAttendance
Who was here
Recorded arrivals and departures for the period you selected.
Look for the gaps
Missing punches and unexplained absences matter more than the totals.
Corrections leave a trace
Editing a record keeps the original alongside the change, which is what makes payroll defensible.
/workforce/leaveLeave
Time off, requested and approved
Requests, balances and the decisions made on them.
Pending first
A pending request blocks someone’s plans, so it is the only urgent state here.
Request leave
The balance is checked as you choose dates, so you find out before submitting, not after.
Approval is a decision, not a formality
Approving changes the schedule and the balance immediately; rejecting should carry a reason.
/workforce/shiftsShifts
The shapes of a working day
Shift patterns define the hours that people can then be assigned to.
By location or team
Coverage is a local question; filter to the group you are actually responsible for.
Define a shift
Start, end and break rules; the same pattern can then be reused across the whole schedule.
Gaps are the point
An uncovered shift is a problem in the future; this page exists to show it before it arrives.
/workforce/scheduleSchedule
Who is on when
Shifts placed against people, across the period you chose.
Week or month
A week shows detail; a month shows whether the rota is fair over time.
Assigning respects leave
Someone on approved leave cannot be quietly scheduled; the conflict is shown as you place the shift.
/workforce/timesheetsTimesheets
Hours claimed
What people say they worked, ready to be checked against attendance.
Unsubmitted and unapproved
These two states hold up payroll; everything else can wait.
Approve what you can verify
Approval is what turns a claim into a number payroll will act on.
/workforce/trainingTraining
What people have learned
Courses, certifications and expiry dates, so a lapsed qualification is visible before it matters.
Record a course
Attach it to the people who took it; the record follows them, not the course.
Expiry is the useful field
A certificate without an expiry date cannot warn you when it stops being valid.
Automation
A workflow starts from a trigger — a new lead, an overdue invoice, a schedule — and runs a chain of steps: assign, notify, create a task, post to a channel, call another system.
Start from a template or draw your own on the canvas, test it with sample data, and follow every run in the execution history to see exactly what happened.
/workflowsAutomations
Work that runs itself
A workflow watches for something to happen and then does the steps you defined.
Enabled or paused
A paused workflow keeps its definition but stops reacting; nothing is lost by pausing one.
Create a workflow
Start from a template when one fits — it is easier to change a working example than to build from nothing.
Read the last run
A workflow that has not run recently is usually waiting on a trigger that never fires.
/workflows/executionsExecutions
Every time a workflow ran
One row per run, with the result and how long it took.
Failures first
A successful run needs no attention; filter to failed ones and work backwards.
Open the trace
The trace shows each step with what went in and what came out, which is where the cause always is.
Finance
Issue and receive invoices, record payments against them and keep every customer and supplier as a party. Each step posts to the chart of accounts, so balances are always up to date.
The journal shows every entry behind those numbers, and the reports summarise a period for the people who need it — without exporting to a spreadsheet first.
/financeFinance
The money side
Accounts, invoices and journal entries, all reading one ledger.
Period and currency
Every figure below belongs to the period shown; changing it changes all of them together.
Balances are derived
Nothing here is typed in; every total is the sum of entries you can open and inspect.
Where to go next
Invoices for what customers owe, journal for corrections, reports for the statements.
/finance/invoicesInvoices
What customers owe you
Each invoice is a claim with a due date, a balance and a history of payments.
Overdue is the filter that matters
Sorting by age of debt tells you who to call today.
Issue an invoice
Issuing posts to the ledger; a draft does not, which is why drafts can be edited freely.
Draft, issued, paid, cancelled
An issued invoice is never deleted; cancelling writes a reversing entry so the trail stays complete.
Record payments as they arrive
Partial payments are allowed, and the remaining balance is what drives the overdue list.
/finance/partiesParties
Who you trade with
Customers and suppliers as the ledger sees them, with their outstanding balance.
Receivable or payable
The same organisation can be both; the filter separates the two questions.
Add a party
Record the legal name and tax identifiers here; invoices read them, not the CRM record.
Link to the CRM account
Linking lets a salesperson see whether a customer pays on time without opening finance.
/finance/accountsChart of accounts
The shape of your books
Every entry has to land in one of these accounts, so the list decides what your reports can say.
Add an account
Add sparingly; a chart with too many accounts is harder to read than one with too few.
Parents summarise children
Post to the leaf accounts; the totals roll up on their own.
A balance is a moment in time
The number you see is as at the end of the selected period, not today.
/finance/journalJournal
Entries in their raw form
Everything the ledger contains, including the entries other modules wrote for you.
Search by account or reference
Most journal questions start from a number you already have on another document.
Manual entries
Use them for corrections and accruals — anything the modules cannot generate on their own.
Debits equal credits
An unbalanced entry cannot be saved; that rule is what keeps every report internally consistent.
/finance/reportsFinancial reports
The statements
Trial balance, profit and loss, and balance sheet, generated from the ledger on demand.
Choose the report and the range
A statement is meaningless without the dates it covers, so they are always shown on it.
Closing a period
Once closed, entries in that period can no longer be edited — corrections go into the next one.
Export for the accountant
The export carries the underlying entries, not just the totals on screen.
Servers & integrations
Servers lists the machines your team runs, with an in-browser terminal and file manager; credentials stay encrypted and access can be limited to specific people.
Integrations connect outside services — messaging bots, calendars, storage — and show whether each connection is healthy.
/serversServers
The machines you run
Hosts registered with the workspace, each with its own credentials and terminal.
Reachable or not
The status here is the result of the last connection attempt, not a live ping.
Register a server
Host, port and how to authenticate; a key is safer than a password and behaves the same here.
A real shell
The terminal is a live SSH session — commands you type run on the machine immediately.
Secrets stay encrypted
Keys and passwords are stored encrypted and are never displayed again after saving.
/integrationsIntegrations
Outside services
Everything the workspace talks to that is not part of it.
Connected or available
An available integration does nothing until somebody connects it.
Connecting grants access
Read what an integration is allowed to do before approving it; that consent is what it acts on later.
Watch for broken links
Expired tokens fail quietly; this page is where that failure becomes visible.
Workspace settings
Settings is where an admin shapes the workspace: invite members, give them roles, switch modules on or off, and choose the calendar, number format and currency everyone sees.
Everyone also has personal settings — profile, theme, language and notifications — that change only their own view.
/settingsSettings
Two kinds of setting
Some choices are yours alone, others change the workspace for everybody — each section says which.
Find the section, not the switch
Settings are grouped by what they affect, so related options stay next to each other.
Your profile
Your name, photo and contact details as colleagues see them across every module.
Appearance
Theme, accent colour and density are personal and take effect immediately, on this device.
Assistant preferences
Whether the assistant appears, which surfaces it may use, and how much it may do without asking.
Workspace
Name, logo and defaults that everyone in this workspace sees — not just you.
Modules
You can hide a module you do not use; you cannot enable one your plan does not include.
Language
Choosing a language switches the whole interface, including right-to-left layout where it applies.
Notification delivery
Choose which events reach you and where — in the app, in the browser, or through a messaging bot.
Subscription
Your plan, how many seats it allows, and the modules it grants. Changing it changes what everyone can open.
Sign-in and security
Your password, second factor and active sessions. Signing out a session takes effect immediately.
People and roles
A role decides what someone can reach; changing it takes effect the next time they load a page.
/crm/teamsTeams
Groups of people
Teams are how work is assigned to more than one person and how visibility is granted in bulk.
Create a team
Name it after the work it does, not the people in it — membership changes, the work usually does not.
Adding someone grants access
New members can immediately see everything the team can see; remove them to take it back.
Roles inside a team
A team lead can manage membership; the workspace role still decides what the module allows.
Still have a question?
Inside the app, the ? next to every page title replays that page’s tour, and the i beside a section explains it. For anything else, we are here to help.
Ready to do this with your own data?
Create a workspace — everything you just saw is there from the first day.