Manage people in the project

Open Users in the sidebar. Team members and testers appear separately, together with active invitations and account join status. Project owner and Project administrator identify customer permissions in the selected project; they do not grant Astor operator access. Owners and administrators can manage both groups and permitted project roles. Product managers can invite testers but cannot grant internal roles.

Invitations and permission changes also check current access after receiving the request. A rejected action does not create an invitation or change a person’s role. Astor rechecks the workspace and removes controls that are no longer permitted. Check the current Users list before retrying.

The project owner counts as an internal team member. Internal teammates use the plan’s included seats. External testers and client reviewers do not consume paid internal seats.

Owners and administrators see used, reserved and available team seats. A pending internal invitation reserves one place for its email address; repeat links for the same person share that reservation. Joining converts it to a used seat. Revoking or letting an unused invitation expire releases the reservation. Tester invitations do not reserve team seats. Existing team members keep access when their number exceeds the current allowance; adding another internal member waits for enough capacity. An earlier unclaimed invitation also needs an available internal place when the person joins.

Group a focused test

In Users, choose Tester invitations. Create an invitation group with a name, website, instructions and end date. This is also where you find active and ended groups across the project’s websites.

Choose Invite a tester on the group to create a personal invitation, or View missions to open its tasks. End invitations closes that group and preserves existing feedback. These controls are available to owners, admins and product managers; they are no longer in Connected tools.

Create a personal invitation

  1. Choose team member or tester.
  2. Enter the person’s email address and, when relevant, name and role.
  3. Optionally choose an active invitation group and a specific Mission.
  4. Add clear instructions and create the invitation.
  5. Review and copy its personal link, or explicitly send its email.

Creating the invitation does not send an email automatically. If sending is unavailable, you can still share the personal link yourself.

The email button shows Queuing… only after you choose Send invitation email. Email queued means the sending request was accepted; it does not confirm inbox delivery.

If all team seats are used or reserved, revoke an unused team invitation or review the project’s plan. An invitation for an existing member does not change their permissions. Additional paid seats are not available yet.

Reuse the tester’s account

The invited person signs in or registers using the matching email address. They do not need their own project, subscription or payment details. The same account can test other projects later, with separate permissions for each project.

If they open another invitation in the same tab, Astor checks that link again. An ended link cannot keep a previous invitation’s project or form on screen.

An accepted task invitation opens the exact project and Mission. Testers see the tools and tasks the project has enabled; they do not see project billing or connected tools.

Review email and access status

Users distinguishes queued, sending, provider-accepted, failed and cancelled emails. Provider acceptance does not prove inbox delivery. Confirm with the tester if needed.

Revoking an unused invitation prevents joining from it. Removing a member stops their project access; their account and other project memberships remain. An old claimed link cannot restore removed access.

Connected tools check the person’s current project permissions on each request. Removing access also ends that project’s API/MCP connections and website feedback sessions. If the person joins again later, they must reconnect their tools. A role in another company or a matching email domain does not grant access to this project.