Administration
Organization Settings
Organization Settings for org admins of a class or a team: members and invitations, organization AI keys, the AI and API switches, two-step sign-in, markings, document templates, single sign-on, class status and the audit log.
On this page
- Concepts
- How to use it
- When and why
- Open Organization Settings
- Set up a class or a team
- Run a class
- Choose what AI may do in an organization
- Turn AI off for an organization
- Allow Kimi K3 or GLM 5.3 in an organization
- Run one organization per department (self-hosted)
- Company defaults (self-hosted)
- Guests (self-hosted)
- When someone needs help you cannot give
- Worked example: a class using the CubeSat EO-1 demo
- Tips and common mistakes
- How it connects to other features
- The Organization Settings page
- Site administrators
- Shortcuts
- Messages
- Limits
- Related pages
Use Organization Settings to manage an organization: a group of accounts for a class or a team. Org admins (the administrators of an organization) manage its members, its AI keys and what AI may do in its projects.
Administering an organization gives no access to project content. Org admins see names, members and settings. To open a project, an owner has to share it with them.
Organization Settings and the Admin page are shown in your interface language (Preferences → Language), like the rest of Holarch.
Org admins do not need two-step sign-in to use Organization Settings, unless their organization requires it for everyone. Site administrators, who run the whole Holarch service from the Admin page, do: Admin opens for them only with two-step sign-in on or a passkey (see Two-step sign-in).
Concepts
| Term | Meaning |
|---|---|
| Organization | A group of accounts for a class or a team. It can hold organization AI keys and AI permissions. Membership gives no access to projects. |
| Org admin | A member who manages an organization's members, invitations, AI keys and settings. An organization keeps at least one org admin. |
| Member | A member of an organization. Members without their own AI key use the organization's key, if there is one, and otherwise the AI included in their plan. |
| Teaching assistant | A role in a class organization only, between Member and Org admin: Class Review, each student's work and Reviewer access to every project of the organization, without managing the organization. See Teaching assistants. |
| Project of an organization | A project whose owner chose the organization under Share → Organization. The organization's settings apply to it. |
| Class organization | An organization that Holarch has marked as a class until a date, usually the end of a term. Its members' projects hold 6 collaborators, its org admins' projects 50, all of them hold 2,000 items, and they do not count toward their owners' active projects. An org admin requests class status; Holarch reviews the request. |
| Password check | Before a change to organization AI keys or single sign-on settings, Holarch asks for your password. The check lasts 10 minutes. |
How to use it
When and why
Organization Settings sits outside the systems engineering lifecycle. Use it to:
- set up the people who work together before a project or a class starts (an organization, its members, its org admins);
- keep AI under control for a class or a team (organization keys, AI permissions, usage by member, monthly limits per member);
- apply shared rules to the organization's projects (two-step sign-in, document markings, document templates, single sign-on);
- get class status for a course, so that student groups can edit one project together.
Open Organization Settings
- Click your initials at the right of the top bar.
- Choose Organization Settings.
You see the organizations you administer.
Other ways in:
- Press ⌘K / Ctrl+K and type Organization, then choose Organization Settings.
- On the Account page, under Organizations, manage organization keys, see usage by member and set monthly AI limits per member.
The menu entry appears once you administer an organization. To get one, create it (below), or ask an org admin to make you Org admin.
Set up a class or a team
Create an organization for a class or a team, add its members, and decide how they use AI.
- Open Account Settings and find Organizations, or, once you administer an organization, open Organization Settings.
- Click Create Organization (Account Settings) or New Organization… (Organization Settings) and enter the name, for example SYSE 682 Fall 2026.
You become the organization's org admin.
- Open Organization Settings and click the organization's row.
The organization's details open in the inspector.
- Under Members, enter an email address.
- Choose Member or Org admin.
- Click Add Member.
An existing account is added at once (“… added.”). Any other address gets an invitation (“Invitation sent to …. They join when they create their account.”), listed under Pending invitations.
- Repeat steps 4–6 for each person.
- Decide on AI. Leave AI permissions at Full, or choose less (see Choose what AI may do in an organization).
Then finish the setup:
- Members already have the AI included in their plan. For more requests, add an organization AI key on the Account page under Organizations → Organization keys. Where paid plans are on sale, the organization key works with the Team plan.
- Ask each project owner to choose the organization in the project's Share dialog under Organization.
Tip: For a team that works commercially, the Team plan gives seats, pooled storage and the organization AI key. See Plan & Billing.
Run a class
A class organization lets student groups edit one project together, and lets the instructor run a project for the whole class. The org admin (the instructor) requests class status; Holarch reviews the request.
- Open Organization Settings and click the organization's row.
- Under Class, click Request Class Status….
- Enter the Course, the School and the End of term, and choose the course Syllabus (PDF or Word, up to 10 MB). Add a Note, for example a link to the course page.
- Click Send Request.
You see "Request sent." and, under Class, "Requested … A Holarch administrator reviews it and emails you."
When the request is approved, you get an email, and Class shows "Class organization until …". The list shows "Class until …" for the organization.
While the class is active:
- projects of the organization owned by a member hold 6 collaborators (owners and editors besides one owner), enough for a group project;
- projects owned by an org admin hold 50, enough for a whole-class exercise;
- reviewers and viewers are never limited: org admins (instructors) and teaching assistants become reviewers of every project of the organization automatically (see Teaching assistants);
- the organization's projects hold 2,000 items (Free plan: 1,000), unless the owner's plan allows more;
- the organization's projects do not count toward their owners' active projects (Free plan: 5);
- storage stays as in each owner's plan;
- org admins and teaching assistants get the Class Review tab (see Contributions): assignments with instructions, a starter project handed out to each group, a due-date lock with extensions per group, rubrics and grades with a gradebook export for Canvas, Moodle or Blackboard Learn, and exam AI windows that turn AI off for the students (see Give instructions and a starter project);
- the instructor package has six example assignments on the EO-1 model with rubrics; instructors and teaching assistants download its solution notes in Class Review.
Each project still needs its owner to choose the organization under Share → Organization. To renew for the next term, choose Ask to Extend… under Class. After the end date, collaborators and items already added stay; new ones follow the owner's plan again. The projects count toward their owners' active projects again: nothing is removed, but an owner over the limit creates new projects only after moving some to the Trash.
Example class starter (optional): Manage Projects → Project Files ▾ → Create Example Class Project creates the LISM Class Starter, a small starting model of a Lake Ice Safety Monitor: the stakeholders, a needs analysis and a requirements document whose sections carry prompts on what belongs there. Use it as it is, change it, ignore it, or choose it as an assignment's Starter project so that Hand Out gives each group its own copy. The same project is a download on the For classes page, to import with Import Project (.json)….
Classroom continuity:
- Students can export their projects at any time: the whole project as a JSON file that imports into any Holarch server (see Back up or move a project), documents as Word, requirements as ReqIF and models as XMI. Viewers can export too.
- If the connection drops while a project is open, work continues in the browser and is saved when the connection is back (see Saving, offline and reconnect).
- The published service targets are 99.95 % monthly uptime for the database and a first support reply within 5 business days on the Free plan; paid plans have shorter targets.
- When the class ends, nothing is removed: collaborators and items already added stay, new ones follow each owner's plan again, and the projects count toward their owners' active projects again.
- Due-date locks and exam AI windows end with the class: students can edit their projects again and AI follows the organization's switches.
- Have students export a copy of their project before each deadline.
Choose what AI may do in an organization
AI permissions has four switches, one per kind of AI request:
| Switch | What it allows |
|---|---|
| Help and how-to | Ask AI answers questions about using Holarch from Help, Docs and the feature list. No project data is sent. |
| Questions about the project | Summaries, explanations, quality and gap checks, and Ask AI about the project. Project content is sent to the AI provider; nothing is changed. |
| Suggestions and changes | Every tool that proposes edits: rewrite, generate, translate, suggest links, functions and flows, risks, test cases. Each change is still previewed. Needs Questions about the project. |
| Reference files in AI | The project's AI reference files are added to the prompts that use them. |
The presets set the switches: Off (none), Help only, Read-only (help and questions about the project), Full (all four). Changing a switch by hand selects Custom.
Read-only still sends project content to the AI provider; it only stops AI from proposing changes. Help only sends no project data.
- Open Organization Settings.
- Click the organization's row and open the AI group.
- Under AI permissions, choose a preset or tick the switches.
- Click Save AI Permissions. You see “AI permissions for …: Read-only.” (with the preset you chose).
The permissions apply to every project of the organization, also with a member's own key or the included AI. Project owners can turn more off for one project under Share → AI permissions, never back on. In the projects, a tool whose switch is off is greyed out with the reason, for example “Changes by AI are turned off for this organization by its administrator.” See AI permissions.
Turn AI off for an organization
Turn AI off when it must not be used in an organization's projects, for example during an exam.
- Open Organization Settings.
- Click the organization's row and open the AI group.
- Under AI permissions, choose Off, then click Save AI Permissions.
- In the dialog, decide on Also turn off API and MCP access, then click Turn AI Off.
AI permissions cover Holarch's own AI features and AI tools that members connect through MCP, such as Claude. Plain API calls (scripts and integrations) use the separate API access switch and can still read the organization's projects. The option turns that off too; it is ticked for a class organization and shown only while API access is on.
You see “AI permissions for …: Off.”, and “AI, API and MCP access turned off for ….” with the option.
While AI is off:
- every AI request for the organization's projects is refused on the server, also with a member's own key or the included AI;
- the organization's keys are not used;
- in those projects, the ✦ AI control is off and shows “AI is turned off for this organization by its administrator.”
To turn AI back on, choose another preset and save.
Allow Kimi K3 or GLM 5.3 in an organization
Holarch's AI is Claude, except on the hosted service for requests from mainland China, Hong Kong, Macau and Taiwan, where the included AI is GLM 5.3 (AI in Mainland China). Kimi K3 (Moonshot AI) and GLM 5.3 (Z.ai) are options you can turn on. In an organization both are off: members cannot add keys for them or use them for the organization's work, and their own Kimi or GLM keys are not used while they belong to it.
- Open Organization Settings.
- Click the organization's row and open the AI group.
- Under Optional AI providers, turn on Allow Kimi K3 (Moonshot AI) or Allow GLM 5.3 (Z.ai). The text under each switch says where requests with it go.
- In Allow …?, click Allow. You see “… allowed.”
Members can then add keys for it (see Kimi K3 and GLM 5.3 in organizations). Keys added earlier work again at once. To stop it, turn the switch off (“… turned off.”); stored keys are kept and not used. Each change is in the organization's Audit Log.
Only providers this server offers are listed. The group is not shown when Holarch sets the organization's AI.
Run one organization per department (self-hosted)
On a self-hosted server, a company usually runs one organization per department, with its own org admins, members and settings. Departments stay apart: an org admin of one organization sees nothing of another. Membership alone opens no project: a project is shared with people, or with a whole organization.
- Create the departments. A site administrator creates each organization with Admin → Organizations → New Organization…, then names its org admins. A person can belong to several organizations, with a different role in each.
- Fill them from one file. In Admin → Invitations → Import from Excel…, one file can name a different organization on each row, and the same person on several rows for several departments. A new person gets one invitation per organization; creating the account from any of them joins every organization they were invited to. An existing member whose row says Org admin becomes an org admin (status Becomes org admin); a file never lowers a role.
- See each department. Admin → Organizations lists the members, org admins and Editors of each organization (people who own or edit a project; each holds a licence seat). Admin → Users has an organization filter.
- Set the rules once. See Company defaults.
- One company sign-in. See Company sign-in for several organizations. With SCIM, the identity provider's groups can also keep each department's members up to date (SCIM groups and departments).
- Company accounts from Active Directory. A site administrator connects the company directory in Admin → Company Directory; people then sign in with their company username and password and land in the organizations their directory groups map to. See Company directory (Active Directory / LDAP). Accounts for people in mapped groups are set up before their first sign-in.
- Limit what a group gets. A group mapping can give its people Viewer or Reviewer access to the department's shared projects instead of Editor, for example for contractors; Editor access beyond the license's seats becomes Viewer. See Access to department projects.
- Work across departments. Share a project with a whole department (Share → Organizations, see Share with a whole organization): everyone in it gets the role while they are a member, also people who join later, and people who leave the department lose it at once. Or share it with each person who needs it (Share), or add a department's current members once, as people, with Share → Add Organization Members… (details). Libraries can be shared with several organizations. Every org admin of a department should be in that organization; site administrators reach every organization from Admin → Organizations without being members. A site administrator who is not a member sees an organization's single sign-on settings read-only, and on a closed network can Mark Verified a domain there.
Company defaults (self-hosted)
Site administrators of a self-hosted server set these once under Admin → Organizations → Company defaults:
| Setting | What it does |
|---|---|
| Require two-step sign-in in every organization | Projects of every organization open only for people with two-step sign-in. While it is on, no organization can turn it off. |
| Sign out after inactivity | The time without activity after which members are signed out. |
| AI permissions | What AI may do in projects. The installation's own AI permissions (AI → AI Settings) stay the limit for everyone. |
| AI providers run from China | Whether organizations allow Kimi K3 or GLM 5.3, when the server offers them. |
| Monthly AI limit per member | Set under AI → AI Spend and Usage; it applies outside organizations and in every organization that follows the company default. |
Every organization follows these, including organizations created later, until its own org admins change one of them. In Organization Settings, each such setting shows Company default or Own setting; Use Company Default goes back to the company's value. When a site administrator changes a default while some organizations have their own value, Holarch asks whether to apply it Only to Those That Follow or to All Organizations. Each change is recorded in the audit log.
Guests (self-hosted)
Project owners can invite people from outside the company, such as customers, to a project (Guests from outside the company). A guest is an account whose email address is outside the company's email domains, that belongs to no organization and is not a site administrator. Site administrators set what guests may do under Admin → Settings → Guests:
| Setting | What it does |
|---|---|
| Allow inviting people outside the company | On by default. Off: Share refuses addresses outside the company, and invitations already sent can no longer be used. |
| Highest role a guest can get | Viewer, Reviewer (default) or Editor. Viewers and reviewers are free on the licence; an Editor guest uses an editor seat. Guests never own projects. |
| Who can invite guests | Project owners (default), Org admins only (owners who are an org admin of the project's organization) or Site administrators only. Site administrators can always invite guests to projects they own. |
| Company email domains | The company's own domains. Verified organization domains and the company directory's domains count too. Addresses in other domains are guests. A subdomain counts as its domain. While no company domain is known, nobody counts as a guest. |
| Allowed guest email domains | Empty: any address outside the company can be invited. Otherwise only addresses in these domains. |
| Guest access ends after | No end (default), 30, 90 or 180 days from when the guest joins a project. The owner renews it in Share (⋯ → Renew Access). A change applies to new guests and to renewals. |
| Two-step sign-in for guests | Same as the company (default): guests need two-step sign-in where the company default or the project's organization requires it for members. Required: always. Not required: never, even where an organization requires it for its members. |
Guests are checked on the server whenever someone invites, resends, accepts, signs up, changes a role or transfers ownership, and when an org admin adds people to an organization. An org admin cannot add a guest to an organization; a site administrator can, and the person is then a member, no longer a guest. Organization shares never reach guests, and their API and MCP tokens reach only the projects shared with them. Require company sign-in for linked accounts and an organization's Require single sign-on for members in the verified domains do not apply to guests: they sign in with email and password, or with Google or Microsoft where the server offers it. Invite-only sign-up does not stop an invited guest.
Admin → Users has a Guests filter and marks each guest Guest; Export Users… has a Guest column; the Editor Seat Report… lists guests without a seat separately. Every change to the settings is in the audit log (Guest settings changed), as are invitation links shown on a server without mail and renewed and ended guest access.
Guests need network access to the server. On a closed network, the simplest way to get a customer's review is to export the requirements documents and DoDAF views as Word or PDF and send them by email; in-app guests need a VPN account limited to the server, a guest network, or the server published through the company's gateway with TLS.
When someone needs help you cannot give
Org admins manage membership, not accounts. For these, the person contacts support (account menu → Contact Us…, or [email protected]):
- a forgotten password: the person uses Forgot your password? on the sign-in screen;
- a lost phone or passkey without recovery codes;
- a project an administrator moved to the Trash that needs to come back (owners restore their own deleted projects from the Trash area of Manage Projects);
- a project whose only owner is gone.
Worked example: a class using the CubeSat EO-1 demo
An instructor runs a systems engineering class in which each team builds on the CubeSat EO-1 demo project.
The instructor:
- Creates the organization EO-1 Design Class under Account Settings → Organizations → Create Organization.
- Requests class status under Organization Settings → Class → Request Class Status…, with the course, the school, the end of term and the course syllabus.
- Adds the students' email addresses as Member in Organization Settings.
- Adds an Anthropic key under Account Settings → Organizations → Organization keys, with a Monthly limit (tokens) of 2,000,000.
Each team lead:
- Creates the demo: Manage Projects → Project Files ▾ → New Demo Project.
- Shares it with the team.
- Chooses EO-1 Design Class under Share → Organization.
Students without their own key now use the organization key instead of their plan's included requests, for example to run Add Measurable Criteria… on requirement 2.5 Safe Mode Recovery. The instructor sees the requests under Usage this month by member.
Before the exam, the instructor sets AI permissions to Off. AI requests in the class projects are refused until another preset is saved. For open-book work the instructor can choose Help only: Ask AI then explains how to use Holarch but sees no project data.
Tips and common mistakes
- Membership is not access. Adding a person to an organization does not share any project with them. Share projects separately.
- Projects join an organization from the Share dialog. Org admins cannot attach a project to an organization. A project owner chooses it under Share → Organization.
- Keep two org admins. An organization needs at least one; a second one can step in when the first is away.
- Add teaching staff as reviewers. Reviewers comment and approve requirements without counting as collaborators.
How it connects to other features
- Collaboration covers project sharing and roles (Owner, Editor, Reviewer, Viewer), which are separate from organization roles.
- AI explains organization keys, which key is used, usage and AI permissions.
- Your account covers sign-in, verification, password reset and Plan & Billing.
- Single Sign-On and SCIM covers the organization's identity provider.
- Contributions covers Class Review for class organizations.
The Organization Settings page
Organization Settings lists the organizations you administer. Click a row, or focus it and press Enter, to show its details in the inspector.
- The page note reads: “Organizations you administer. Choose what AI may do in their projects, and manage members.”
- Columns: Name, Your role, AI (the AI permissions preset: Off, Help only, Read-only, Full or Custom) and Class (“Class until …” or —).
- With none: “You administer no organization.” and “Create one with New Organization.” New Organization… above the list creates one.
- In a class organization, a Class Review tab appears next to Organizations.
- The Audit Log tab shows what changed in your organization. See Audit log.
People who administer no organization see “This page is for administrators.”
Organization details
The details start with the name and a summary (members, the AI preset such as “AI: Read-only”, class), then come in groups you open and close: Members (open at first), Plan and storage, AI, Access and sign-in, Documents, Class and Delete organization. Each group shows its state on its line, for example AI · Full. Your browser remembers which groups you leave open.
The parts in the table below sit in these groups: Members holds Members and Pending invitations; Plan and storage holds Team plan and Storage; AI holds AI, Organization keys and Usage this month by member; Access and sign-in holds API access, Single sign-on and Sign-in, and SysML v2 repositories (Allowed repository hosts, one host per line, that the organization's SysML v2 projects may pull from and push to; empty allows any public https host; Save Hosts); Documents holds Document marking and Document templates.
| Part | Contents |
|---|---|
| Header | The name, and “You are an org admin” with the summary (members, AI preset, class). |
| AI | AI permissions: the presets, the four switches, the note “Read-only still sends project content to the AI provider; it only stops AI from proposing changes. Help only sends no project data.” and Save AI Permissions. Below it, unless Off: “Members use the AI included in their plan, their own Anthropic key or the organization's key, within these permissions. Project owners can turn more off for one project in Share. …” When Off: “Off. AI is turned off for this organization by its administrator: AI requests for its projects are refused, also with members' own keys.” |
| Team plan | Where paid plans are on sale: “No team plan. Members use their own plans…”, “Team plan active: N seats, M in use.”, or “Team plan (…) ends on date. The seats end then; the organization, its members and projects stay.” Below it: “The organization AI key works with the Team plan.” See Plan & Billing. |
| API access | Allow API and MCP access to this organization's projects. When on: “On. Members use their own API tokens and AI tools (MCP) in the organization's projects, within their project roles.” When off: “Off. API and MCP requests for the organization's projects are refused, for every member's token.” Turning it off asks Turn API Access Off first. See API and MCP. |
| Single sign-on | Verify the organization's email domains, connect its SAML identity provider, turn single sign-on on or require it, and create SCIM tokens so the identity provider manages accounts. See Single Sign-On and SCIM. |
| Document marking | The organization's marking (header, footer, notice), or “None.”, under “Printed on every export of this organization's projects unless a project or document sets its own.” Edit Marking… changes it. See Mark documents and exports. |
| Document templates | The organization's document templates. Rename, switch Default (one per document type, preselected in the Create Document wizard) or Remove. See Documents. |
| Sign-in | Require two-step sign-in for this organization's projects. When on: “Required. The organization's projects open only for people with two-step sign-in on; this includes collaborators from outside the organization.” When off: “Not required. Each person decides whether to use two-step sign-in.” Turning it on asks Require Two-Step Sign-In first; the toast says how many members have not set it up yet. Members without it are asked at their next sign-in. See Two-step sign-in. Below: Sign out members after inactivity, a list with 8 hours (default), 4 hours, 2 hours, 1 hour, 30 minutes and 15 minutes; the toast reads, for example, “Inactivity sign-out set to 30 minutes.” Members get a warning 2 minutes before; a member of several organizations gets the shortest time; API tokens and connected apps are not affected. The group line shows the choice, for example “Sign-out after 30 minutes”. See Sign-out after inactivity. |
| Class | “Not a class organization. Projects follow their owner's plan.”, “Class organization until …” with the class rules, or “Class status ended on …. Collaborators already added keep their access.” Request Class Status… or Ask to Extend…; a pending request shows “Requested …. A Holarch administrator reviews it and emails you.” |
| Members | The note “Org admins manage this organization's members, invitations and AI setting. They have no access to other organizations or to site administration.” Each member with a role list (Member, Org admin) and Remove. Below: an email field, a role list and Add Member. Open Members View shows the members in the full page width (see Members View). |
| Pending invitations | Email, role and expiry, with Revoke (“Invitation revoked.”). |
| Storage | With a Team plan: “used of limit used (n%). N seats × 2 GB, shared by the seated members: projects they own and their clipart.” with a bar, By member (Member, Used) and Largest projects (Project, Used, Limit). Without one: “No team plan. Each member's storage follows their own plan.” |
Remove asks “Remove … from …? They lose the organization's AI keys. Project access does not change.” Changing a role shows “… is now Member.” or “… is now Org admin.”
In the AI group, below the switch, org admins see Organization keys and Usage this month by member: the same as the organization’s card on the Account page under Organizations. Above the table they set the members' monthly AI limit (Unit, Default limit per member, Save), and each row has Limit with Edit… and Use Default (see Member limits). When a member reaches the limit, the org admins get a notice.
Delete an organization
Org admins delete an organization at the end of its details: Delete Organization…, then type its name and click Delete Organization.
- Deleted with it: the members list, pending invitations, organization AI keys, single sign-on and SCIM settings, document templates and marking, and class review data. This cannot be undone.
- Members keep their accounts, plans and projects. The organization's projects stay with their owners, without an organization.
- With a Team plan the deletion is refused: “This organization has a Team plan. Cancel it in Plan & Billing first; you can delete the organization after the plan ends.”
One Team plan per account
An account holds one Team plan. In the details of another organization you administer, the Team plan part reads “No team plan. Members use their own plans. Your account uses the Team plan of organization; an account holds one Team plan. To give this organization a Team plan, buy it from another account that administers it.”
Members View
Open Members View in the Members group opens the organization's members in the full page width:
- ‹ Organizations goes back to the list.
- A table of the members with Name, Email, a role list (Member, Org admin, and in a class organization Teaching assistant) and Remove. Filter members narrows it by name or email.
- Add Members: paste the addresses of a class or team into Email addresses, one per line or separated by commas, choose a Role and click Add Members. People with an account join at once; the others get an invitation by email. The line under the box says how many were added and invited, and lists any address that was not added with the reason; those addresses stay in the box to correct and send again.
- Import from Excel… under Add Members invites many people from a spreadsheet (see Import members from Excel).
- Pending invitations with Email, Role, Expires and Revoke.
Import members from Excel
Import from Excel… (in the organization's Members group and under Add Members in the Members View) invites many people at once from an Excel (.xlsx) or CSV file, one person per row. Site administrators find the same button under Admin → Invitations, where a row can name any organization, or none for an account only.
- Click Import from Excel…. Download Template saves an Excel file with the columns and how to fill them in.
- Fill in one row per person:
| Column | What to enter |
|---|---|
| Required. | |
| Name | Optional. Their sign-up form starts with it. |
| Language | Optional. The interface language of the new account: a code (de, ja, pt-BR) or a name (German, Deutsch). |
| Organization | Optional. Here: empty or this organization's name. In Admin → Invitations: any organization, by name or ID; empty invites to an account only. |
| Organization role | Optional. Member (default), Org admin, or Teaching assistant (class organizations only). |
| Site admin | Admin → Invitations only. Yes makes the new account a site administrator; Holarch asks to confirm. |
Header names may be in any case. Other columns are ignored and named in the preview.
- Choose the file under Excel or CSV file. The preview lists every row with its status and the counts. Nothing is sent yet.
| Status | Meaning |
|---|---|
| New invitation | Gets an email with a link to create an account (valid 7 days); joins the organization when the account is created. |
| Joins organization | Has an account and joins at once. |
| Already a member | Nothing changes. |
| Becomes org admin | Already a member; the Organization role column makes them an org admin. |
| Has an account | Admin → Invitations, no organization named: nothing changes. |
| Bad address | The Email cell is not an email address. |
| Duplicate in file | The address is on an earlier row for the same organization, or this row names no organization and the address is on an earlier row; only that row counts. |
| Unknown organization | No single organization has this name or ID. |
| Not allowed | For example the Site admin column from an org admin, another organization, or a teaching assistant outside a class organization. The note says why. |
| Unreadable value | A role or Yes/No cell Holarch does not know. |
| No free seat | The team's seats are all in use. Add seats in Plan & Billing. |
Show narrows the table to the rows that will be invited or to the others. Choose Another File starts again.
- Click Invite N People. The results show what happened to each row. Download Results (.xlsx) or (.csv) saves them.
On a server that sends no email (a self-hosted server without mail), the results show each new person's invitation link, once. Copy or download them then, and send each person only their own link: anyone with a link can create that account. On a self-hosted server, accounts are free; a seat is taken only when someone owns or edits a project.
Each import is recorded once in the audit log with its file name and counts, beside the usual entry for each invitation.
Organization keys and usage
Organization keys and usage by member are in the organization’s details in Organization Settings and on the Account page under Organizations:
- Organization keys: add, test, remove. Without a Team plan the note reads “The organization AI key works with the Team plan. This organization has no Team plan, so its keys are not used.” (where paid plans are on sale).
- Members.
- Usage this month by member: Member, Requests, Tokens, Cost (estimate), with a total.
See AI.
Request Class Status
The dialog reads: “A Holarch administrator checks the request and marks … as a class until the end of the term. Projects of a class organization owned by members hold 6 collaborators; projects owned by org admins hold 50. Each holds up to 2,000 items. Reviewers and viewers are not limited.”
| Field | Notes |
|---|---|
| Course | Up to 120 characters, for example SYSE 685 Systems Engineering. |
| School | Up to 120 characters. |
| End of term | A date after today. |
| Syllabus | Required: the course syllabus as a PDF or Word file (.pdf, .docx or .doc), up to 10 MB. Holarch checks the file's content, not only its name. Only Holarch administrators can open it, to verify the class; it is deleted 30 days after the request is approved or declined. |
| Note | Optional, up to 500 characters: a link to the course page, the number of students. |
Send Request shows “Request sent.”
Audit log
The Audit Log tab lists what changed in the organizations you administer, newest first. It needs a Team plan or class status; other organizations show “The audit log comes with the Team plan.” and where to upgrade (Plan & Billing).
Included events:
| Events | What they cover |
|---|---|
| Organization | Created, renamed, two-step sign-in requirement, sign-out after inactivity, document marking, model repository hosts, document templates, project folders (created, renamed, moved, deleted), audit log exports. |
| Members and invitations | Members added, removed or leaving, role changes, invitations sent and revoked. |
| Projects and sharing | Projects of the organization: created, moved to the Trash, restored, deleted permanently, transferred, linked to the organization, marked; project invitations and their answers, role changes, members removed or leaving; pushes to model repositories; library releases; projects moved between the organization's folders. |
| Baselines and change requests | Baselines approved, signed, renamed or deleted; change-request votes. |
| Single sign-on | Domains, SAML settings, single sign-on on or required, SCIM tokens and the accounts the identity provider created, changed or removed. |
| AI and API | Organization AI keys added, changed or removed; AI permissions (with the switches before and after, also when a project owner changes a project's) and the API switch. |
| Class review | Class organizations only: class requests, assignments, roll-up exports and views of a member's contributions. |
Not included: sign-ins and sign-outs, changes people make to their own accounts (password, email, two-step sign-in), network addresses and browsers, and edits to project content. An organization that needs sign-in records uses its identity provider's logs (Single Sign-On and SCIM).
- Which projects: projects that belong to the organization now, with their earlier events. A project removed from the organization leaves the log with its events.
- People: members of the organization and of the project show with name and email; other people show as “External collaborator: name”. Changes Holarch administrators made to your settings show as “Holarch administrator”.
- Filters: Organization (when you administer several), Events, Project, Person, From and To (UTC days, both included). With nothing found: “No events match these filters. Widen the date range or clear the filters.”
- Columns: Time (your local time; UTC in the tooltip), Action, Person, Project, Target (for example the invited email) and Details. Click a row, or focus it and press Enter, to show the event's details.
- Paging: 100 events at a time; Load More shows older ones.
- Export CSV… saves the events that match the filters (all pages, up to 50,000) as
<organization> audit log <from>–<to>.csvwith the columns Time (UTC), Action code, Action, Person, Person email, Project id, Project name, Target and Details. It asks for your password when the last check is more than 10 minutes old. The export itself is recorded in the log. Values that a spreadsheet would run as formulas are written as text. - Events are kept for 400 days.
Site administrators
Site administrators run the whole server from Admin (the account menu → Admin). Its Audit Log page has Export CSV…: the events that match the filters (person, action, dates), up to 50,000, as a CSV file with time (UTC), action, person, target, project, address, browser and details. The export is recorded in the log.
Shortcuts
| Keys | Action |
|---|---|
| ⌘K / Ctrl+K then Organization | Organization Settings |
| ⌘K / Ctrl+K then Organization Audit Log | The Audit Log tab |
| Enter on a focused row | Show its details in the inspector |
| Esc | Hide the inspector |
Messages
| Message | Meaning and fix |
|---|---|
| Confirm Your Password dialog | Holarch needs a recent password check before a change to organization AI keys or single sign-on, and before an audit log export. Enter your password; the check lasts 10 minutes. “The password is wrong. Try again.” means the password did not match. |
| “This person is already a member of the organization.” | No change needed. |
| “The file has N rows; one import takes at most 1,000. Split the file, then import each part.” | Import from Excel takes up to 1,000 rows. Split the file. |
| “The file has no Email column. Use Download Template for the columns, then try again.” | The first row must name the columns, with one called Email. |
| “Choose an Excel (.xlsx) or CSV (.csv) file.” | Save the spreadsheet as .xlsx or .csv. Older .xls files are not read. |
| “An organization needs at least one administrator.” | Make another member Org admin before changing or removing the last one. |
| “Only an administrator of this organization can do this.” | You are a member, not an org admin, of this organization. |
| “This page is for administrators.” | You administer no organization. Create one under Account Settings → Organizations, or ask an org admin to make you Org admin. |
| “This tab could not be shown. Reload the page.” | The tab failed to load. Reload the page. |
| “This range has more than 50,000 events. Choose a shorter date range.” | The audit log export holds up to 50,000 events. Set From and To to a shorter range and export each part. |
| “The audit log comes with the Team plan.” | The organization has no Team plan or class status. Buy a Team plan in Plan & Billing, or request class status. |
| “Attach the course syllabus (PDF or Word).” | A class request needs the syllabus. Choose the file under Syllabus. |
| “The file is not a PDF or Word document. Choose a .pdf, .docx or .doc file.” | The file's content does not match its name, for example a renamed file. Save the syllabus as PDF or Word and choose it again. |
Limits
- The password check lasts 10 minutes per session.
- Organization invitations are valid for 7 days.
- Import from Excel: up to 1,000 rows and 20 MB per file.
- Organization names are up to 100 characters.
- Audit log: kept 400 days; 100 events per page; exports up to 50,000 events.
- Class requests: course and school up to 120 characters, note up to 500; syllabus up to 10 MB (.pdf, .docx or .doc), kept 30 days after the decision.