Settings

The Hana Settings Module centralizes all configuration and administration tools for both individual users and organizations. It provides a tabbed interface where people can update personal details, manage organizational information, control security policies, review subscription plans, and personalize their interaction with Hana’s interface. Role-based permissions ensure that sensitive actions are restricted to the appropriate administrators while still giving all users a single location to view essential information.

Accessing the Module

• Navigation: Open the left-side navigation panel and select Settings.
• Direct links: Each tab is deep-linkable via /settings?tab=<tabName> so teammates can jump directly to a section.
• Responsiveness: The layout adapts seamlessly to desktops, tablets, and mobile devices.

Tab Navigation and Role-Based Access

The Settings Module exposes up to five tabs. Tabs appear only when allowed for the current user’s role. Trying to access a restricted tab directly prompts a “not authorized” notice.

Tab	Purpose	Who Can View	Who Can Modify/Perform Actions
Profile	View personal account information	Everyone	Read-only
Organization	Configure organization details and preferences	Everyone	Admins, Super Admins, Domain Owners
Billing	Manage subscription plan, seats, and invoices	Admins, Super Admins, Domain Owners	Same as view
Security	Set organization-wide access and security controls	Admins, Super Admins, Domain Owners	Same as view
User Settings	Customize individual experience (dock, controls, etc.)	Everyone	Everyone (some controls restricted to admins)

Profile Settings

Purpose: Display immutable information about the signed-in user.

Key Features

• Shows display name, email, role, tenant ID, and Hana access status.
• Information is read-only; no edits or saves are required.
• An informational note explains how role and bot access are managed.

Typical Use Case

Confirm your assigned role or verify whether Hana access is active.

Organization Settings

Purpose: Maintain organization-level data and language preferences.

Key Features

• Organization details: name, website, location, country, industry type, company size, and an “About” field for mission statements or descriptions.
• Preferred language for Hana’s prompts and responses. Supported options include Spanish, Italian, Portuguese, German, French, Dutch, Hindi, English, Japanese, Russian, and Arabic.
• Invocation history toggle to allow or disable storage of invocation history for compliance or privacy.

Access Control

Only Admins, Super Admins, and Domain Owners can submit updates. Other roles can view but not edit.

Validation and Feedback

• The form validates mandatory fields before submission.
• Success and error notifications clearly indicate outcomes.

Typical Use Case

An organization admin updates the company’s website and preferred language, enabling invocation history for audit purposes.

Billing Management

Purpose: Oversee subscription plans, seat assignments, and financial records.

Key Features

• Plan overview showing current plan tier, renewal date, and plan-specific icon.
• Upgrade button enabled when DNS verification or admin status allows. Button text changes to “Edit Plan” when already on the highest tier.
• Dedicated invoice dialog listing past invoices with server-side pagination. Columns include invoice number, status, total amount, creation date, and download link.
• Seat synchronization note clarifying that all users share the same plan and seat count must match active users.

Security

Only Admins, Super Admins, and Domain Owners can access billing functions. Others see an authorization message.

Typical Use Case

A Domain Owner checks the invoice history and upgrades the plan after verifying DNS ownership.

Security Controls

Purpose: Govern how Hana interacts with users and how the organization can manage its data.

Key Features

• Interaction toggles for 1–1 interaction, group interaction, private chat command, and response metadata.
• “Danger Zone” section permanently deactivates the organization, removing data and ending the subscription. Requires entering the organization name to confirm. Action logs the user out and redirects to the homepage.
• Each toggle triggers loading indicators and success/error notifications.

Role Restrictions

Only Admins, Super Admins, and Domain Owners may adjust settings or deactivate the organization.

Typical Use Case

An admin enables response metadata and disables private chat commands to tighten data handling policies.

Personal Settings

Purpose: Tailor the user’s personal experience within Hana.

Key Features

• Gmail Rundown Daily Update toggle presently disabled while the feature undergoes revamp. A note informs users it will return once improved.
• Response Control Card: Admin-level roles can enable a card that gives finer control over Hana’s responses during interactions.
• Dock Visibility and Position: Toggle to show or hide the on-screen dock that houses Hana’s quick actions and choose its location (e.g., bottom-left, bottom-right). Changes persist across sessions.

Typical Use Case

A standard user chooses to hide the dock on small screens and repositions it to the top-right on a workstation.

Notifications and Feedback

• Inline validation highlights errors before submission.
• Toast notifications display successes (e.g., “Details updated successfully”) and errors (e.g., “User details not found”).
• Loading indicators overlay forms during network operations to prevent duplicate submissions.
• Authorization alerts inform users when they lack permission to perform certain actions.

Localization & Accessibility

All labels, messages, and alerts support multiple languages; switching the preferred language updates the interface accordingly. Semantic HTML, keyboard navigation, and responsive design provide accessibility across devices and assistive technologies. Visual cues (colors, disabled states) help distinguish actionable elements from read-only fields.

Typical Workflow

1. Open Settings from the side navigation.
2. Review the available tabs; select one based on the task (e.g., Billing).
3. If necessary, confirm role permissions or request admin access.
4. Make adjustments, using inline validations to correct issues.
5. Submit changes where applicable and watch for success or error toasts.
6. Navigate to another tab or return to the dashboard when done.

Key Benefits

• Centralized Administration: Users and admins manage everything in one place.
• Role-Based Safety: Sensitive operations remain protected while basic information stays accessible.
• Scalability: Tabbed design and server-side pagination support organizations of any size.
• Personalization: Individuals can tailor their experience without affecting others.