Check the address.
Open your invitation and check the email address and expiry. Use the invited account in the intended workspace. Joining the public waitlist does not make you a member.
Bring your team
Bring your team.
Start well together.
Give people the right invitation, clear access and one small task. Help each teammate find their work and understand how the team checks a result.
- People
- Shared work
- First contribution
Prepare a simple welcome
The right address.
A clear first step.
An active administrator sends invitations from the existing workspace. Before sending, check its enabled sign-in methods and human-seat capacity in Admin.
Choose the first Project or Team and a person who can answer setup questions. Give new teammates the workspace address, their intended role and a small outcome to work on.
Read workspace invitation HelpFor the workspace administrator
Invite with
the right role.
Open Admin → Team and review the members and pending Invitations before starting. Use Member for ordinary participation. Choose Admin only for people who need workspace administration.
The bulk form uses one role for everyone newly invited. Send separate groups when people need different roles.
Manage pending invitations- 01
Open Invite your team.
Use the form in Admin → Team inside your workspace.
- 02
Add the intended addresses.
Paste up to fifty distinct email addresses, separated by new lines, commas, semicolons or spaces. Repeated addresses count once.
- 03
Choose Role for everyone.
Check Member or Admin before sending. Admin gives all newly invited people in this group workspace administration access.
- 04
Send and inspect each result.
Choose Send invitations. Review queued invitations, existing members, pending invitations and entries needing retry.
Check what happened
A sent request.
A separate acceptance.
Read the saved result before sending again. The Invitations list shows the address, role and expiry. Resend provides a replacement; Revoke closes an invitation that should no longer grant access.
| Result | Next step | Keep in mind |
|---|---|---|
| Queued invitation | Check the recorded result, then give the recipient the workspace details. | Queued does not prove the message arrived or that the person accepted. Confirm membership in the member list. |
| Existing member | Check their Active or Suspended status and the work they need to access. | Another invitation is not the fix for an existing member’s Project, Team or sign-in problem. |
| Usable pending invitation | Use the existing invitation. Choose Resend if a replacement is needed. | Retrying a bulk list skips usable pending invitations; it does not resend each message. |
| Entry needing retry | Read the per-address result, resolve the reported problem and retry where appropriate. | The retry skips existing members and usable pending invitations, preserving their roles and links. |
An expired, revoked or already used invitation cannot be accepted. Ask an administrator to check its state and the member list, then resend when appropriate. Revoking a pending invitation and suspending an existing member are separate actions.
For the invited teammate
Join as yourself. Find your work.
Keep the invitation and workspace address together. If something is unclear, ask the administrator to check the account and invitation before trying another route.
Use an enabled method.
With email/password, follow the invitation page to choose your name and password. With a provider, use the invited address. Your workspace decides which methods it offers.
Find your workspace sign-inOpen Home and Work.
Find Projects and Teams under Work. Check that you can open the place chosen for your first task and its linked documents. Save your own timezone in Account settings → Preferences.
Read your first workspace stepsA role is part of the setup
Help them reach
the work they need.
Accepting an invitation establishes workspace membership. Check work access separately, using the teammate’s own account.
Choose Member or Admin.
Administrators manage roles and Active or Suspended status in Admin → Team. The workspace must keep at least one active administrator.
Check the first work home.
Check Project visibility, direct grants and Team membership. Access may come from more than one source. Removing one grant may leave another route to the Project.
Check the source too.
A work link does not grant source access. Private workshops require participation, including for administrators. Review drafts stay with their author; editions use named reader access.
Make the first contribution useful
A small outcome.
Something to check together.
Choose a task small enough to finish and review. Put it in the Project or Team responsible for the result. Save the context and acceptance criteria, choose assignees and complexity, and add a due date only for a real deadline.
Agree who checks the output. Move the item to the configured review stage while that check remains. Complete it after the criteria pass and the result is linked.
Read how to define a work itemNew teammates can find the handover guide.
- Context
- The team needs a clear starting point for a support handover.
- Acceptance
- The guide names the handover owner and is linked from the Project’s documentation. A new teammate can open it with their own account.
- Review
- Try the link together, check the owner is correct and record the result on the work item.
Build the habit in the workspace
A little guidance.
Room to learn by doing.
Home’s Get started with Tellenze card gives each member their own walkthrough. Administrators and Members have different lessons. You can start any checkpoint, pause the guidance or skip a step for now.
You choose what to create and save each form yourself. Resume or replay lessons through Account settings → Preferences → Onboarding. Keep a simple team habit: define the work, record useful decisions and review the result.
Read the onboarding walkthrough- 01
Read before beginning.
Open the Definition and linked guidance. Ask about missing context before starting.
- 02
Keep progress beside the work.
Use Conversation for questions, decisions and meaningful updates.
- 03
Make a blocker clear.
Mark blocked work and explain the dependency and next action needed.
- 04
Close with evidence.
Check the acceptance criteria, link the output and record how it was verified.
Connect an agent when useful
Start with a read.
Keep the choice yours.
A member can authorize a compatible agent client through MCP using their own membership. Review the consent, use the workspace’s connection details and start with work the member can already access.
Ask it to read the task and relevant guidance before proposing a change. Where Required Context applies, supported actions need the pinned reading and a current receipt. That receipt does not prove understanding or correctness.
Prepare an agent connectionAn illustrative first request
“Read this onboarding task and the guidance I can access. Summarize the goal and completion checks, then tell me what is missing.”
Review the answer and the proposed next step. Connections follow current member access; a prompt cannot grant access to hidden work.
Read conversational agent onboardingA few useful details
Help each person get started.
The invitation says Queued. Has my teammate joined?
Queued does not prove delivery or acceptance. Inspect the invitation result and check the member list. Use Resend when a replacement invitation is needed, rather than repeatedly submitting the same bulk list.
What if someone was invited at the wrong address?
Ask an administrator to check the invitation and existing membership. Revoke an unused invitation that should no longer grant access, then invite the intended address. Matching email addresses alone do not link separate workspace accounts.
Why can someone sign in but not open the Project?
Workspace membership and Project or Team access are separate. Check visibility, direct access grants and Team membership, then the linked document or provider source. A copied link grants no access.
Do teammates need an agent to complete onboarding?
People can define and follow work directly. Home’s walkthrough lets them skip a checkpoint for now and resume it later. Connect an agent when it helps the work; ChatGPT access follows its separate private pilot guidance.
What happens when a suspended member returns?
An administrator can set the member back to Active so they can sign in using an enabled method. Suspension revokes MCP authorizations, so those agent connections need fresh authorization. Restoring membership does not restore the revoked connections.
A good first week
A useful contribution.
A shared way forward.
Give each person a clear place to start, someone to ask and a result the team can review together.
Keep your next step clear
Find the guide for your next step.
COME TAKE A LOOK
A little less busy.
A lot more together.
Curious? Join the waitlist and see how we welcome your team.
Tell us a little about your team. We’ll explain the next steps and invite you when we have capacity for your workspace.
Join waitlist Start with your email. No payment needed to join.