Explain the path
Give requesters a source they can check.
Them AI for IT
Make the right IT guidance easier to find
Recurring questions interrupt the person who knows the answer. Bring approved setup instructions, request policies, and troubleshooting guidance into shared rooms, so teammates understand the next step without confusing an explanation with permission to act.
Mac-only for now. Free during the beta (invite-only).
IT roomShared room
You with your team
What do I need before requesting this tool?
Them AI with company contextInclude the business need, intended use, and responsible team. The software policy routes data handling questions to security and purchasing questions to the budget owner before the request proceeds.
↗ Example software policyReview with IT operations
After human approvalSoftware request process
A useful record for the next person.
Illustrative workflow. Not a live conversation.
The work gets better when the context stays.
Good judgment belongs
with the whole team.
Reduce missing context
Help teammates prepare a more useful question.
Keep judgment human
Leave approvals and changes with responsible owners.
In the day-to-day
Work your team can bring to Them AI.
Start with the question. Keep the source. Make a person responsible for what comes next.
IT room Example 01
Where should I start with setup?
Start with the approved onboarding guide, then confirm the required setup with the IT owner. The guide identifies which steps you can complete and which need their assistance.
↗ Example setup guidanceSetup guidance
Help teammates understand approved setup instructions before asking for help. Cite prerequisites and the support owner, then let IT confirm any step that could affect access, security, or a managed device.
See how the workflow fits
- Bring
- Setup guide
- Review
- IT specialist
- Keep
- Guidance summary
IT room Example 02
What should my software request explain?
Explain the use case, intended users, and data handling needs. The request policy sends those details to the IT owner, who can identify the required security and purchasing reviews.
↗ Example request policySoftware requests
Make the request policy understandable before it becomes another incomplete message. Ask which business details are needed, identify the reviewers, and prepare an outline without treating it as an approved purchase.
See how the workflow fits
- Bring
- Software policy
- Review
- IT owner
- Keep
- Request outline
IT room Example 03
What should I include when asking for help?
Describe the observed behavior, the approved steps attempted, and where the process stopped. That gives the support owner a starting point and makes the remaining question clear.
↗ Example support checklistSupport context
Use reviewed troubleshooting guidance to organize what happened and what was tried. Keep secrets and personal device details out, then give the IT owner a clear question and safe supporting context.
See how the workflow fits
- Bring
- Sanitized symptoms
- Review
- Support owner
- Keep
- Support outline
IT room Example 04
Who needs to review my access request?
The access policy names the system owner as reviewer. Explain the business need and requested scope, then follow the designated approval path before anyone provisions the access.
↗ Example access policyAccess guidance
Explain who reviews an access request and why the policy exists. Keep the approved process available for repeated questions, while actual identity checks, approvals, and provisioning remain in the authorized systems.
See how the workflow fits
- Bring
- Access policy
- Review
- Access owner
- Keep
- Process explanation
These are example workflows to evaluate, not customer results. Connected agents use their own tools; Them AI is the shared context and review workspace.
From useful work to reusable knowledge
The conversation is
only the beginning.
Memory keeps the facts and decisions. Skills keep a way of working. People decide what deserves to become a shared reference.
Meet Rooms and the Collective- 01
Bring the context
Example software policy
- 02
Make the human call
IT operations reviews the sources and proposed record.
- 03
Keep the method
Request preparation
Make it real
Start with the common setup question
Bring one approved guide and the IT owner who handles its exceptions.
Discuss a design partnership
Before you begin
A few things
worth knowing.
Does Them AI provision access?
No native provisioning is promised. External agents own execution and must use their own authorized systems.
Can we store credentials here?
No. Human access is organization-wide today. Keep credentials, security findings, and restricted incident records outside the shared workspace.
What is a sensible beta pilot?
Mac-only for now. Free during the beta (invite-only). Start with general setup guidance that everyone may read.
What does the current beta include?
Shared rooms, memory with sources and review status, reusable skills, and MCP access for connected agents. Mac-only for now. Free during the beta (invite-only). Human room and memory access is organization-wide. Client-scoped MCP feeds restrict agent retrieval to that client's approved records plus approved firm-wide material. Do not treat a room as a private boundary for individual members. Read the access boundaries.
Bring one real workflow
Make the next project
better informed than the last.
Start with a question your team keeps answering. Bring the sources, the people who know, and the decisions worth keeping.
Mac-only for now. Free during the beta (invite-only).