Track 5. Teams and Administration: exercise sheet
For team leads and tool administrators. One practice task and a few questions per chapter, to work through after each video. Print this page from your browser, or work on screen. The answer key starts on a new page at the end.
Before you start
- Take first
- Chapter 1.1 and chapter 1.7 Sharing and Roles.
- Plan
- Free for organizations and roles; chapters tagged Individual plan or Team plan use paid-plan features.
- Project
- A Plant Inspection Drone project in an organization you administer.
5.1 Organizations and Members
Watch chapter 5.1 (2:45)
Practice
On the CubeSat EO-1 demo project:
- Open Account Settings, find Organizations, enter
EO-1 Practice Teamand click Create Organization. - Open Organization Settings, click the organization's row, and under Members add a second email address (a colleague's or another address of your own) as Member with Add Member.
- Open your EO-1 demo project (if you have none, create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)). Click Share, choose
EO-1 Practice Teamunder Organization, and click Done. - In Manage Projects, select the organization's folder tree, click New Folder, name it
Spacecraft, and drag the EO-1 project onto it. - Open Account Settings → Plan (or Plan & Billing) and note how many editors and items your projects may hold.
You're done when EO-1 sits in the Spacecraft folder of the organization's tree and the second address is listed as a member or a pending invitation.
Questions
- You added a colleague to your organization. Can they open the EO-1 project now?
- Who can make a project part of an organization?
- Why keep a second org admin?
- What does an org admin see of the organization's projects?
5.2 Roles, Reviewers and Approvals
Watch chapter 5.2 (1:56)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (if you have none, create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)). Click Share, invite a second email address as Reviewer, and click Invite.
- Select requirement 2.4 Target Slew (status Draft) and set its Status to In Review in the inspector's Workflow group.
- Open Needs & Requirements → Approvals, click 2.4, and click Approve. Then click 3.4 Bus Regulation, click Reject…, and enter the reason
Name the source of the 2% tolerance. - Edit the description of 2.4 Target Slew: change
60 secondsto45 seconds. - Open Approvals again, and on 3.4 Bus Regulation click Reopen.
You're done when 2.4 Target Slew is back on the Approvals list with the note Text changed after approval, and 3.4 Bus Regulation is In Review again.
Questions
- Why invite the people who sign off on requirements as reviewers rather than editors?
- What happens when someone edits the description of an approved requirement?
- Your program wants three named approvers and a change board before an approved requirement may change. Is the Approve button enough?
5.3 Sign-In, Two-Step and Passkeys
Watch chapter 5.3 (2:35)
Practice
On the CubeSat EO-1 demo project:
- Open Account Settings and go to Two-step sign-in. Click Add a Passkey…, enter your Current password, click Continue, and confirm in your browser.
- Click Rename next to the new passkey and give it the name of the device it lives on.
- Click Set Up Authenticator App…, scan the code with your authenticator app, enter its 6-digit code, and click Turn On.
- Click Download for the recovery codes, store the file away from your phone, and click I Saved the Codes.
- Under Signed-in devices, read each session's browser and last activity, and click Sign Out on any you do not recognize. Then sign out and sign in again with a passkey, and open EO-1.
You're done when the Two-step sign-in card reads On, your passkey is listed with its device name, and you signed in with it.
Questions
- Does adding a passkey turn on two-step sign-in?
- You lost your phone and have no recovery codes. What now?
- Your organization requires two-step sign-in. What happens to a collaborator from outside the organization who has not set it up?
5.4 API Tokens and Connecting ClaudeUses features of the Individual and Team plans:
Watch chapter 5.4 (2:39)
Practice
On the CubeSat EO-1 demo project:
- Open Account Settings → API tokens. Under New token, name it
EO-1 report, choose Read only, 30 days and Selected projects with EO-1 ticked, and click Create Token; copy the token. - Run the
curlexample from Token Created to list your projects, and check that only EO-1 comes back. - Click Connect an AI App…, choose Claude, and follow the steps. On Connect Claude to Holarch, choose Read and propose changes, Chosen projects with EO-1, and an end of 30 days, then click Allow.
- In Claude, ask:
Propose a test case in EO-1 that verifies requirement 2.4 Target Slew. - Open EO-1, choose ✦ AI ▾ → Review “…”…, untick anything you do not want, and click Apply Selected.
- Back in API tokens, click Revoke on
EO-1 report, and under Connected apps click Disconnect if you do not need Claude connected.
You're done when EO-1 has the new test case from the proposal and the token is gone from your list.
Questions
- When do you use a token, and when a connected app?
- You are a reviewer in a project and use a read-and-write token. Can a script change that project?
- Claude proposes five changes. What has changed in the project?
- How do you cut off every token and app at once?
5.5 AI for an OrganizationUses features of the Individual and Team plans:
Watch chapter 5.5 (2:21)
Practice
On the CubeSat EO-1 demo project:
- Open your EO-1 demo project (if you have none, create it: Manage Projects → Project Files ▾ → New Demo Project → CubeSat (Guided systems engineering)). Choose ✦ AI ▾ → AI Settings… and read Key in use and Included AI.
- Open Organization Settings, click your organization's row, and open the AI group. If your organization has a Team plan, add an Anthropic key under Organization keys with a Monthly limit (tokens).
- Clear Allow AI in this organization's projects, decide on Also turn off API and MCP access, and click Turn AI Off.
- Open EO-1 (it must belong to the organization: Share → Organization) and check the ✦ AI control and the Share dialog.
- Tick Allow AI in this organization's projects again.
You're done when you saw “AI is turned off for this organization by its administrator.” in EO-1, and AI is on again.
Questions
- A member has their own Anthropic key, and the organization has one too. Which key answers their request?
- AI is off for the organization. Can a member still use AI in its projects with their own key?
- AI is off, but a member's Claude, connected through MCP, still reads the projects. Why?
5.6 Data Ownership and Account Recovery
Watch chapter 5.6 (2:03)
Practice
On the CubeSat EO-1 demo project:
- In Manage Projects, open EO-1's row menu ⋯, choose Export this project…, keep the options, and click Export JSON.
- Choose Project Files ▾ → Import Project (.json)… and pick the file. Open the copy and check that the SRS still lists its SRR Baseline under Version ▾.
- Back in Manage Projects, choose ⋯ → Delete this project… on the copy, then restore it from the Trash area below the list with Restore.
- Open Account Settings → Signed-in devices and click Sign Out Other Devices.
- Delete the copy again when you are done.
You're done when you have restored the copy from the Trash and opened its SRR Baseline.
Questions
- What does a project export hold, and where can it go?
- You delete your account. What happens to a project you share with two colleagues where you are the only owner?
- You suspect someone learned your password. Is changing it enough?
Answer key
5.1 Organizations and Members
- No. Membership in an organization gives no access to its projects. The project's owner shares it with them in the Share dialog and gives them a role.
- Only one of the project's owners, under Share → Organization. Org admins cannot attach projects; they manage members and the organization's settings.
- An organization always needs at least one org admin, so the last one cannot be removed or demoted. A second one can manage members and settings when the first is away.
- Names, members and settings, but no project content. To open a project, an owner has to share it with them.
5.2 Roles, Reviewers and Approvals
- Reviewers read, comment and approve or reject requirements without being able to edit the model. They are free on every plan and do not count toward the project's editor limit.
- It goes back to In Review with the note Text changed after approval, so an approval always matches the words that were approved. Changing other attributes does not reopen it.
- No. Approve records one decision on the requirement's status. Required approvers, change boards and their rules belong to change requests, and those approval rules are part of the Team plan.
5.3 Sign-In, Two-Step and Passkeys
- No. A passkey signs you in on its own, without email or password. Two-step sign-in is a separate switch; once it is on, a passkey also serves as the second step after a password.
- Email support from your account's address. Support checks who is asking, then resets two-step sign-in; set it up again right after you sign in.
- The organization's projects do not open for them until they set it up, with a passkey offered first. The requirement covers everyone who opens those projects, not only members. Requiring it for an organization is part of the Team plan.
5.4 API Tokens and Connecting Claude
- A token is for scripts and clients that send a fixed header; it is shown once and you store it. A connected app signs in on Holarch's consent screen without a pasted token, ends after one year at most, and is listed under Connected apps.
- No. A token acts as you, within your role in each project, so a reviewer or viewer only reads.
- Nothing yet. The changes wait as a proposal; you review them, untick what you do not want, and Apply Selected makes the rest one undo step. Deletions and changes to approved or baselined items start unticked.
- Sign Out Everywhere, or a password reset, disconnects every connected app and revokes every token. An org admin can also turn off API and MCP access for the organization's projects.
5.5 AI for an Organization
- Their own key. The order is your own key, then the organization's key, then the AI included in your plan.
- No. Every AI request for the organization's projects is refused on the server, with any key, including the included AI.
- AI tools connected through MCP use the separate API access switch. Tick Also turn off API and MCP access when turning AI off, or turn off API access on its own.
5.6 Data Ownership and Account Recovery
- The whole project as a JSON file, with its baselines and, depending on the options, comments and history. It imports into any Holarch server as a new project with a new ID, owned by whoever imports it.
- The deletion is refused until you transfer ownership or remove the other members. Projects where you are the only member close with the account and are kept for one year for record-keeping, then erased.
- Changing it signs out your other devices but leaves connected apps and tokens working unless you tick Also disconnect apps and revoke API tokens. A password reset or Sign Out Everywhere always ends every session, app and token.
Published by Holarch