Getting Started for End Users

This guide is for anyone logging into SAVHN for the first time as an invited team member, not as an organization administrator. It covers activating your account, setting up your profile, and finding your way around the platform.

Activating your account

You'll receive an email invitation from your organization's admin containing a signup link. This link is single-use and expires after a set period — if it has expired, ask your admin to resend the invite.
Follow the link and set a password (or, if your organization has single sign-on configured, authenticate through your organization's identity provider instead).
On first login, SAVHN presents a short profile setup flow before dropping you into the main workspace.

Profile setup

Complete the following before your profile is considered ready:

Name and display photo — used throughout Chat, Meetings, Timeline, and anywhere your name appears next to activity.
Contact details — phone and secondary email, used for notifications and (if enabled) two-factor recovery.
Notification preferences — choose which modules send you email notifications versus in-app only. You can revisit this at any time from Profile → Notifications.
Time zone — defaults to your organization's time zone but can be set individually; this affects how Meetings, Timeline, and due dates across Projects and Tickets are displayed to you.

Your profile also shows read-only fields populated by your organization's admin, such as your department, manager, and employee ID (if HRMS is enabled) — these are managed centrally and aren't user-editable.

SAVHN's main navigation shows only the modules that are:

Enabled for your organization, and
Permitted for your role (or individually granted to you).

If a colleague sees a module you don't, it's typically because your role doesn't include it — ask your admin if you believe you need access. Because navigation is data-driven, it's normal for two users at the same organization to see meaningfully different menus.

A typical navigation set for a standard employee includes:

Area	What it's for
Timeline	Your personal activity feed: tasks, mentions, approvals awaiting you
Chat	Direct messages and team channels
Meetings	Scheduled meetings, agendas, and notes
Documents	Shared and personal file storage
Projects	Projects and tasks you're a member of
Tickets	Support or internal tickets assigned to or raised by you
Reports	Dashboards you have view access to

Modules like HRMS, Payroll, Finance, and CRM appear based on your role — most standard employees see a self-service subset (e.g. their own payslips and leave balance in HRMS) rather than the full administrative surface.

Working across modules without losing context

Because SAVHN uses a single identity and a shared record model across modules (see Platform Architecture Overview), you'll frequently move between modules while working on the same underlying thing. A few patterns make this smoother:

Cross-links inside records. A Project task can reference a related Ticket; a CRM deal can link to the Meeting where it was discussed; a Document can be attached directly to any of these. Clicking a cross-link takes you straight to the related record rather than requiring you to search for it in another module.
@mentions work everywhere. Mentioning a colleague in a Chat message, a Meeting note, or a Ticket comment notifies them the same way and links back to your name and profile consistently.
Your Timeline aggregates across all of this. Rather than remembering to check Tickets, then Projects, then Meetings separately, Timeline surfaces anything across your enabled modules that needs your attention, in one place, roughly in priority order.

Customizing your workspace

Most list views (Tickets, Projects, CRM records, and others) support light personalization that doesn't affect other users:

Column selection — show or hide columns relevant to how you work.
Saved filters — save a frequently used filter (e.g. "My open tickets, high priority") as a named view you can return to.
Default landing view — some modules let you choose which view (list, board, calendar) opens by default when you enter that module.

These preferences are stored against your profile, so they follow you across devices but never change what a colleague sees when they open the same module.

The AI Assistant

Most organizations enable the AI Assistant, available from a persistent icon in the navigation. It can answer questions about your own records ("how many leave days do I have left," "what tickets are assigned to me"), draft content, and take simple actions you have permission for (e.g. submitting a leave request) when asked in natural language. It only operates within your existing permissions — it cannot see or act on data your account can't already access.

Timeline is designed as your default landing view — it aggregates items needing your attention across every module you use, so you don't have to check each module separately.
Global search (top of the navigation) searches across every module you have access to — records, documents, chat messages, and people.
Notifications (bell icon) surface approvals, mentions, and assignments; clicking one deep-links directly to the relevant record.
Most list views across modules support saved filters and column customization — changes you make to a list view are personal and don't affect what other users see.

Getting help

Use Documents → Knowledge Center if your organization has published internal how-to content.
This Documentation Portal covers platform-wide behavior; your organization's admin may also maintain internal guides specific to your workflows.
If something looks broken rather than merely unfamiliar, see Common Login & Access Issues or Troubleshooting Module & Integration Issues before contacting your admin.

Mobile and multi-device access

If your organization has enabled mobile access, the same permission model applies identically on mobile as on desktop — you will not see anything on your phone that your role doesn't already grant on the web application, and vice versa. Notification preferences (email versus in-app/push) are configured once in your profile and apply across every device you're logged into. Logging out of one device does not log you out of others; use Profile → Active Sessions if you ever need to revoke access from a lost or old device rather than assuming a single logout covers everything.

Understanding record ownership and assignment

As you start creating and being assigned records across modules (a Ticket assigned to you, a Project task you own, a Deal you're the CRM owner of), it's useful to understand the distinction:

Owner generally refers to the person primarily accountable for a record's outcome, and is what most "my records" filters key off.
Assignee may differ from owner in workflows where work is delegated — for example, a Ticket owned by a team lead but assigned to a specific agent for resolution.
Watchers/followers (where a module supports them) receive notifications on a record's activity without being the owner or assignee — useful for staying informed on something adjacent to your direct responsibilities without cluttering your own task list.

Getting comfortable with this distinction early helps you understand why your Timeline surfaces certain items and not others — it's generally built around what you own or are assigned, not everything you merely have visibility into.

Checklist for your first day

Set your password and log in
Complete your profile (photo, contact details, time zone, notification preferences)
Review your Timeline for any pending items assigned before you joined
Confirm you can see the modules relevant to your role — flag any gaps to your admin
Explore Global Search and the AI Assistant
Join relevant Chat channels for your team

Once you're comfortable with the basics, if your role includes any administrative responsibility over modules, continue to the Admin Guide sections covering role management and module configuration.