Organization

The organization page is the company level that sits above your individual workspaces. It's where an owner or admin manages people across the whole company, groups work into departments, and sets standards that flow down to every department. Use the tabs across the top to move between areas.

Overview

The company at a glance:

• Seats used — how many seats are taken against your plan's limit (Enterprise is unlimited). The owner uses a seat too.
• Company profile — legal name, domain, website, industry, billing address, and a short description. These are your company's billing and legal details.
• Org brand — a default logo, colors, tagline, portal label, and footer applied across every department's public portals. You can leave it as a default each department may override, or enforce it so departments can't change it.

Members

Everyone in the company and how they join:

• Invite — invite a colleague by email as Admin or Member. If they don't have an account yet, they're prompted to sign up.
• Members table — see roles (Owner, Admin, Member), promote or demote, and remove people. Removing someone takes away their access to every workspace in the org.
• Join requests — approve or decline people who requested to join, choosing their role.
• Invite link — a shareable link that sends a join request when opened; regenerate it to invalidate the old one.
• Org roles — role templates for the whole company. Departments link their own roles to a template so name and colour stay in sync everywhere.

Departments

Departments are your workspaces, viewed from the company level. Create a new department, and control access for org admins: when enabled, org admins are automatically full admins in every department; when disabled, they need their own role in each. The org owner is always an admin everywhere regardless.

Defaults

Company-wide defaults that every department inherits. For each one you can enforce it (lock it) so departments can't override, or leave it as a starting point they may change:

• Response deadlines (SLA) — a company-wide floor per priority. Locking enforces it over every workspace, project, and role.
• Invitation sender — who invitation emails come from: the Sennith system sender, your own verified org domain, or a company-owned SMTP configuration.
• Customer portal visibility — what guests versus logged-in customers see in the portal: hidden, a list of project names, or list plus full detail.
• Customer notification starting value — the default for newly claimed customer accounts (every update, a digest, or portal-only). Customers can always change their own preference, so this one can't be locked.
• SMTP default — the sender preselected when emailing customers.

Resources

Company-owned senders. Set up company SMTP profiles that every department can use as "Company" for sending — a send-only resource, never taken over from someone's personal profile.

Public views

Guardrails and oversight for public project pages across the company:

• Public view guardrails — company-wide rules such as requiring password protection, capping how much detail public pages may reveal, and starting new projects offline. New or changed configurations must meet the rules; existing violations stay editable and are flagged for you to fix.
• Public views (all departments) — an aggregated read-through of every department's public pages, including departments you're not a member of.
• Sender domain — verify your own domain (DKIM/SPF) so customer update emails go out under it instead of the system sender.

Analytics

Company-wide metrics across every department — views, updates, messages, answer rate, and median response time — shown both as headline numbers and broken down per department.

Plan

Your organization's subscription. Review the plan, usage, and billing period, and upgrade, downgrade, or switch billing here.

API keys

Manage organization-level API keys — company-wide keys for automation and integration. Everyday working keys are created inside each workspace instead.

Security & activity

Company-wide security and a governance log:

• Security policy — require two-factor authentication for all members, with a grace period after which people without it are prompted to set it up.
• Activity — a log of governance actions: members, roles, departments, billing rights, settings, sender-domain verification, and public-view bulk updates.
• Billing permissions — decide who can pay and who can delegate that right. The owner always has both; you can also grant billing to all admins at once.

Danger zone

• Transfer ownership — hand the organization over to an existing admin or member. You become an admin, and they become the new owner.