Seats and roles: who on your team can see what
The person who claims becomes admin, colleagues at the domain join read-only, and only organisation admins see plans and invoices. Editors and analysts do not.
Three roles and one boundary
A claimed organisation on infratoapp has seats with roles: admin, editor and analyst. The person who claims the listing becomes admin. Colleagues who sign in with an address at the same domain join the workspace read-only until an admin changes that. Organisation admins see plans and invoices; editors and analysts do not. The workspace also shows who in it is outside your domain.
The roles fit an organisation where one listing is read by sales, edited by marketing and paid for by finance, and those are different people.
None of this costs anything. Seats and roles come with a claimed listing, with no plan needed, and the pricing page shows them among the screens of the free workspace.
The roles do not touch the public page. A reader sees the same listing whoever edits it, and seats have nothing to do with where a product ranks.
How people arrive in the workspace
The domain is the door. A colleague signing in with a work address at your domain gets the shared workspace straight away: every listing the organisation owns, its analytics and its vendor intelligence. They arrive read-only.
Promotion is a decision a person takes, not one a mail server takes. Having an address at the company is proof of employment, not proof that anyone wants you rewriting what readers see. An admin decides who edits.
Someone who arrives at the claim page after a colleague claimed is told so and asked to request a seat. The admin’s address is masked, so a stranger who guesses your domain cannot learn whose mailbox runs the account.
The domain rule cuts both ways. Somebody at a subsidiary or parent company with its own domain does not arrive through yours, and if they are added, they show as outside it.
What separates the roles
The published line is about money. Plans and invoices, on the Plans and billing screen, are for organisation admins only. An editor or an analyst does not see what the organisation pays; what else separates the two is set in the portal.
Beyond that the vendor pages do not set out a full permission table, so check in the portal before assuming an editor can submit a change request or an analyst can download the leads list. Plan your roles around the one rule that is stated.
The same split applies to buying. A plan belongs to the organisation, but only an admin can see that it exists in the portal, so an editor who wonders why a Featured card appeared may have to ask an admin.
Analyst seats suit people who read the totals and never touch the listing, such as a sales lead checking opt-ins. They are also a safe default for anyone who asks for access without saying why.
People outside your domain
The vendor guide lists seats and roles together with who is outside your domain. An agency, a contractor or a parent company with a different domain can be a member, and the workspace shows them as outside it.
Review that list when contracts end. Removing a seat is the admin’s job, and an agency that ran last year’s launch does not need this year’s leads.
Someone outside your domain proved nothing about your company by signing in. That is why the workspace marks them, and why each such seat should be one an admin can explain to a colleague who asks.
Our own staff are a separate case. When a member of staff views the portal as you, for support, they cannot open the named leads list, because it holds readers’ email addresses.
A layout to start from
Keep at least two admins, so the account does not depend on one inbox; one of them should be whoever approves invoices, since they see them anyway. Make the people who write the description, answer category questions and draft a Pro Profile editors.
Give everyone who only reads the numbers analyst seats. The Intent signals page says the leads list is visible to members of the organisation, which is a reason to keep membership to people with a reason to be there.
When someone leaves, remove the seat. Their access came from the domain, but a former employee may keep a working mailbox for some days, and an admin is the only person who can close that gap here.
Review the seat list whenever a plan starts. An Intelligence plan puts named readers’ email addresses in front of every member, so membership matters more after it than before.
When the only admin leaves
An organisation with one admin depends on one mailbox. If that person leaves and their address is closed, nobody left in the workspace can see plans or invoices, and the person who decided roles is gone. Colleagues can still join read-only through the domain.
The claim page offers one way back: a colleague who finds the listing already claimed can ask the admin for a seat and, if nobody answers, ask us to look. That is a person handling it, which takes longer than an admin changing a role, so the cheaper fix is a second admin before it is needed.
Plans are not tied to the person either. They belong to the organisation, so a departing admin does not take a Pro Profile or a Featured card with them. What leaves with them is the only view of the invoices.
Check this on the day the listing is claimed. The first admin is whoever clicked the link, and that may be someone in marketing or a founder who will not want to handle invoices for long.
What we could not answer
- ⚑The vendor pages publish one rule about roles, that only admins see plans and invoices; the full permission table for editors and analysts is not published, so this post does not guess it.
- ⚑How a member outside your domain is added is not described on the public pages.
What this rests on
infratoapp, “Seats and roles: who on your team can see what”, read 27 October 2026. https://www.infratoapp.com/blog/seats-and-roles-who-can-see-what
Questions people ask about this
Who becomes admin when a listing is claimed?
The person who claims it. They prove control of the company domain with a work email and become the admin of the organisation’s workspace. Colleagues who sign in later from the same domain join read-only until an admin gives them more.
Can editors and analysts see what we pay infratoapp?
No. Plans and invoices are visible to organisation admins only. Editors and analysts can work with the listing and its figures without seeing the Plans and billing screen, so finance staff who need invoices should hold an admin seat.
Can infratoapp staff see our named leads list?
No. When a member of staff views the vendor portal as an organisation, for support, the named leads list cannot be opened, because it contains readers’ email addresses. The list is visible to members of the organisation itself.
These render as FAQPage structured data · answers are filled from the same live figures
Read next
Every claimed listing shows thirty-day totals of views, comparisons, outbound clicks and opt-ins against the thirty days before. Counts under 5 are withheld.
There is no checkout and no card on file. You email, a person creates an order and sends an invoice, and the plan switches on when the invoice is marked paid.
A dispute works when it points at a page we can re-read that says something different. An assertion without a page leaves the published value where it is.