Skip to main content
Version: 2026.05

Onboard your organization

End users cannot run jobs on the Istari Digital Platform until an organization administrator has invited them and granted tool access, and until IT has connected an agent with the integrations your team needs. User tutorials such as Web app 101 assume that work is already done.

In this tutorial you invite a pilot team, grant the functions they need, and confirm a non-admin account can run @istari:extract on a spreadsheet.

By the end you will:

  • Invite colleagues and confirm they can sign in
  • Grant tool access for the integrations your tutorials use
  • Verify that a non-admin user can run @istari:extract on a spreadsheet

Time: ~20 minutes (agent setup is a prerequisite — see below).

Prerequisites​

  • Organization administrator access — the Admin shield in the sidebar footer and Agents in the main sidebar. See the Administrator Guide.

  • A connected agent with Open Spreadsheet on Agents → All Agents (healthy status, module listed). The org admin does not install or start the agent in the web app; IT does that on a host. Your only agent setup step, if IT asks for credentials, is to generate a token:

    1. Agents → Generate Token → copy the value once (Agents).
    2. Send the token securely to IT for stari agent init and agent startup.
    3. After the agent runs, it appears on All Agents automatically — no separate “register agent” action in the admin hub.

    IT handles installation, modules on disk, stari agent init, and starting the agent. If All Agents is empty, complete the token handoff with IT and wait before continuing this tutorial.

Pick one colleague to be your tutorial user — a normal account without org admin access. You will verify job execution as that user in the last step.

Download the sample spreadsheet used in Web app 101 (your tutorial user will need it later):

Step 1 — Confirm admin access​

  1. Sign in to the Istari Digital web app.
  2. Check the sidebar footer for the Admin shield icon.
  3. Click Admin (or go to /admin). The admin hub opens with Users selected by default.

If the Admin icon is missing, you do not have organization administrator access. Contact your organization owner — see Granting admin access.

Step 2 — Invite users​

  1. On Users, confirm the organization dropdown shows your organization.
  2. Click Add user (+ icon) in the top-right.
  3. Enter Email address, First name, and Last name for your tutorial user (and any other pilot members).
  4. Click Invite.
  5. Ask invitees to accept and sign in. On the Users page, watch the Invited tab until they appear under Active.

Each invited user needs Active status before you can grant tool access or run the verification step.

See User Management for edit, deactivate, and other user actions.

Step 3 — Grant tool access​

Users can run functions only for tools you allow.

  1. Open the Admin hub → Users.
  2. Find your tutorial user. Open the ⋯ menu on their row.
  3. Select Manage Tool Access.
  4. Expand Open Spreadsheet (or the tool your pilot uses).
  5. Enable @istari:extract and any other functions the team needs.
  6. Click Save.

Repeat for each user who will run jobs in the pilot.

See Manage tool access in the Administrator Guide.

Step 4 — Verify job execution (as your tutorial user)​

Sign in as the tutorial user (not your org admin account) and run one extraction. This is the same check Web app 101 depends on.

  1. Click Files in the sidebar.
  2. Upload Group3-UAS-Requirements.xlsx.
  3. Open the file and click Create Job.
  4. Select open_spreadsheet → @istari:extract.
  5. Click Execute Function.
  6. Wait until the job status is Completed.

If the job Failed:

  • On Agents → All Agents, confirm an agent is Idle (or healthy) and lists Open Spreadsheet under Installed Modules. If no agent appears, work with IT — see the agent prerequisite above.
  • On Admin → Users, confirm the tutorial user has @istari:extract under Manage Tool Access.

What you set up​

PieceWhy it matters
Active usersReal accounts for tutorials and pilots — not shared admin logins.
Connected agent (prerequisite)Jobs run on an agent IT installs and starts; you only supply a token if IT needs one.
Tool accessEven with an agent, users cannot run functions you have not granted.
Verified extractProves the full path works before the team opens Web app 101.

What's next​

  • Web app 101 — Your tutorial user can start the end-user digital thread tutorial.

  • Python Client 201 — Script the same extract flow once jobs work in the web app.

  • Administrator Guide — Reference for admin hub sections (integrations, secure connections, infosec, agent pools).

  • Configure partner sharing (Secure Connections) — Set up Sending and Receiving Connections so Editors can share models with partner organizations.

  • Planned org-admin tutorials will cover monitoring jobs and agent pools and external app connections.