Open the Team page for the correct verified company to review members, invite a colleague or change access. Owners and admins have different controls, and an invitation is not yet a membership. Choose the recipient and role before sending; the colleague should use their own account with the invited email address.
- Tools listed
- 13,000+
- Submissions decided within 24 hours, last 30 days
- 94%
- Listing reads by AI assistants answering a person, last 30 days
- 66,000+
- Listed tools that are free or freemium
- 53%
Toolradar's own database, read 22 November 2026. Listing is free; it does not guarantee visits, rankings or AI answers.
This guide was first published and updated on 6 November 2026. The team page, invitation handler, acceptance page and member controls were inspected on that date.
Toolradar is part of Dupple and sells vendor services and sponsored placements. Team access is an account-management function, not a paid endorsement. Our commercial disclosure and editorial policy explain the wider relationship. An account role does not establish product quality, editorial approval or legal ownership of a business.
Start with the company and the person
Use an individual Toolradar account, then check which company is active in the dashboard. A person can belong to more than one company. An existing selection can therefore be different from the company named in an invitation. Review the company name before changing a role or removing a colleague.
The Team page requires membership of a verified company. If the business has not been connected to an authorized account, follow the company-claim guide first. If another colleague already controls the company, ask an authorized owner or admin to invite you. Submitting another product through the software-listing workflow is a separate task and does not replace a team invitation.
Decide what the colleague needs to do. A person reviewing analytics and a person administering company access may have different responsibilities. Do not assume that the word Member means every company feature is read-only: individual workflows apply their own permission checks. The table below concerns team-management controls specifically.
Choose between the three team roles
Toolradar data: the current team controls use 3 roles, Owner, Admin and Member. Invitations can create Admin or Member access; Owner is a separate role-change option for an existing colleague. These are implementation definitions checked on 6 November, not the number of employees at a vendor or a count of active customer accounts.
Table: Team-management permissions in the inspected company routes, checked 6 November 2026. Feature permissions outside team management can differ.
| Role | Team actions available in the inspected workflow | Boundary to keep in mind |
|---|---|---|
| Owner | Invite an admin or member, change another member's role, review pending invitations and remove another member subject to the owner safeguards. | The role-change route rejects changing your own role. |
| Admin | Invite an ordinary member, review or revoke pending invitations and remove another non-owner member. | An admin cannot invite another admin, change team roles or remove an owner through these routes. |
| Member | View the company's member list. | The team invitation and member-management actions require an admin or owner. |
The team permission definitions record the relevant source files and rules. They do not contain a real company's roster, email addresses, invitation tokens or delivery results. Use them to understand the workflow rather than infer access to every part of the product.
The OWASP authorization guidance, read 6 November 2026, recommends giving people the access their work requires and reviewing it over time. That is a useful planning principle here. It is not an independent audit or certification of Toolradar's permission implementation.
Invite a colleague with the intended address
An owner or admin can use Invite Team Member on the Team page. Enter the colleague's own email and choose the available role. The selector starts with Member; the Admin option is shown to an owner. The form gives an owner 2 role choices and an admin 1. Review both fields before submitting because the recipient account and the granted role matter after acceptance.
The current handler normalizes the invitation address and checks whether that person is already a member. It also refuses another unused, unexpired invitation to the same address for that company. A refusal is therefore not necessarily an email-delivery problem. Inspect existing members and pending invitations before trying to create another request.
Toolradar data: a new invitation is given an expiry 7 calendar days after creation by advancing its calendar date. This is not an invitation completion rate or a guarantee of seven full working days. The pending list includes unused invitations whose expiry remains in the future; an expired or accepted invitation is not part of that list.
Invite a person whose access has been agreed within the business. A shared inbox, forwarding rule or copied account password is not a substitute for selecting the intended colleague. This guide does not send an invitation, enroll a person or change anyone's current access.
Separate invitation creation from email delivery
An invitation can exist even when its email could not be sent. The current interface distinguishes the failed-send result and can present a link for the authorized inviter to share with the intended recipient. Resolve the displayed issue before assuming that pressing Send Invite reached the colleague.
A successful send response also does not prove inbox placement, reading or acceptance. Resend's explanation of missing email, read 6 November 2026, distinguishes provider processing from acceptance by a receiving mail server, and explains that even a delivered email can be filtered into another folder. Those are email-delivery distinctions, not measured Toolradar delivery rates.
If the recipient cannot find the message, check the address and the displayed invitation state first. The colleague can search their own mail folders; a provider or account issue may need support. Share a valid invitation only with the person it was created for. Do not put the invitation link into a public ticket, a product description or a screenshot intended for publication.
Accept while signed in to the matching account
The acceptance page checks the invitation, whether it has already been used and whether it has expired. It sends a person who is not signed in through login with a return path to the invitation. When the signed-in email differs from the invited address, the page explains the wrong-account problem and offers a sign-out path back to the invitation.
Opening a valid invitation while signed in with the matching account can create the membership immediately. Do not treat that page as a harmless preview before deciding whether the person should join. Read the company and role in the invitation before following it. No live acceptance link was opened for this guide.
After acceptance, review the company selection in the dashboard. The invitation's company and a previously selected active company can differ. Confirm the member appears in the intended company's team list rather than relying only on a welcome screen or assuming the active company changed automatically.
The acceptance workflow also handles an existing membership without granting a new role over it. If the person needs different privileges after joining, use the authorized role controls instead of repeatedly inviting them. Keep invitation acceptance separate from connecting an assistant, which introduces its own authorization and connection state.
Change access when responsibilities change
An owner can review another existing member's role and select the intended replacement. The current controls include Owner as a role-change option, while the invitation form does not directly invite an owner. Verify the person and company carefully when assigning responsibility for future administration.
The member-management routes reject removing yourself or changing your own role. They also contain checks against demoting or removing the last owner. If the remaining owner is leaving, establish who should retain ownership before removing access. If nobody authorized can administer the company, use the claim and access route or contact support rather than creating duplicate companies.
Removing a member and revoking a pending invitation address different states. Removing a member concerns existing membership; revoking an invitation cancels the unused route to joining. Review both lists when a person no longer needs access. A pending invitation should not be described as an employee who already has company access.
Team membership also differs from assistant connections and other credentials. When responsibilities change, review the separate connection workflow as well. This guide does not claim that deleting a membership independently audits every old session, external system or key. Handle a listing update, analytics review or customer-review invitation through its own controls and purpose.
A fictional team handover
For the fictional company Cedar Metrics, an owner wants a colleague to review product activity while another person will administer the team. The owner first checks that Cedar Metrics is active, confirms each person's account address and decides which responsibilities require administrative access. No actual staff member or customer record is described here.
The colleague follows the invitation with the matching account, then checks the selected company. Before the original administrator leaves, the owner reviews roles, existing memberships and unused invitations. The team separately reviews connected assistants. The example gives no real delivery time, success rate or security outcome; it shows the decisions to make at each stage.
What we could not verify
We inspected the current source for the Team page, invitations, acceptance and member-management routes. We did not invite a real colleague, enter an authenticated company account, accept an invitation or perform an independent security or email-delivery audit. The role table covers these team controls, not every permission or offboarding consequence. Interface behavior and rules can change; consult the current company dashboard and privacy information when handling account details.
Frequently asked questions
Who can invite another person to a company?
An owner or admin of the verified active company can invite an ordinary member. Only an owner can invite an admin in the inspected workflow.
How long does an invitation remain valid?
The current handler sets its expiry 7 calendar days after creation. The pending list shows only invitations that remain unused and unexpired.
Does an invitation mean the colleague has joined?
No. Creation, email processing and acceptance are separate states. Review the member list after the intended person accepts with the matching account.
Can an admin change another person's role?
The inspected role-change route requires an owner. An admin's team controls include inviting ordinary members and removing another non-owner member.
Can I remove myself or change my own role?
The current member-management routes reject those actions. Arrange the change with another authorized owner and preserve ownership before a handover.
Spotted an outdated price or a wrong fact? Suggest a correction: we check it against the vendor's own page. Work for one of these vendors? Claim your listing to update it yourself.
Review your company team
Sign in, confirm the active verified company and review its members and pending invitations before changing access.
Some offers on this page may be paid placements or contain affiliate links.