Team and access

This page covers your team: the people who have a role on the account, such as seeing billing, managing sites or inviting others. Your authors, the people credited on a site's articles and paid a share, are a separate roster with a separate invite; see For authors.

Two rosters, not one

The two rosters are stored, invited and removed separately. Taking someone off your team doesn't touch their author credit, and taking them off a site's author roster doesn't touch their team role. One person can be on both, for example a co-founder who is an admin and a credited author.

Roles

Role	Sees	Can change	Can't
Owner	Everything.	Everything.	Nothing is reserved from an owner. An account can have more than one; see Owners.
Admin	Every site, earnings, billing, the audit log and activity.	Site settings, domains, pricing, which paths toll, the team roster, API keys, webhooks, notification settings, support threads.	Anything that decides where money goes (see below), the plan, paying invoices, deleting a site, security policy, data requests.
Billing manager	Invoices, the current plan, and the team roster.	Pay invoices, manage the card on file, open billing support threads.	Choose or change the plan (the owner decides it, you pay it), sites, earnings.
Analyst	Every site, earnings, billing, the audit log and activity.	Run and schedule exports.	Any setting.
Developer	Every site.	Which paths toll and which articles read free, and API keys.	Earnings, billing, webhooks (they carry every payment's amount), the team.

Author is not a team role; see For authors. Who may spend or manage an organization's buyer balance is a separate table: see Buying for an organization.

Each role sees only the pages it can use. A page it can't use says so, and a setting it can't change is locked with the reason shown.

Owners

Add a second owner. If the only owner loses their login, nobody can change where your sites are paid, change the plan, or add anyone. The team tab warns you while you're the only one.

To add one, invite the person to the team first. Once they've accepted, pick them under Owners in Settings → Team and choose Make owner. You'll be asked for your password if you haven't signed in in the last few minutes, and every owner gets an email saying who was added.

Owners are listed in the order they became one, and that order matters:

• You can remove an owner listed after you straight away.
• Removing an owner listed before you waits 72 hours. They're emailed at once and can cancel it.
• You can step down yourself at any time, as long as another owner remains. You stay on the team as an admin.

This stops a compromised login from locking the real owner out: any owner it adds is newer than you, so you can remove them at once, and they can't cancel anything you do.

Money stays with the site's owner

Some settings decide where a site's money goes or who gets paid: its payout wallet, its credits source, per-article wallet pins, co-author splits, where unclaimed author shares go, and its settlement network. The site's owner changes them at once. No team role can: an admin can see the payout wallet but can't change it.

An owner of the account who doesn't own that site can change its payout wallet, settlement network, co-author split and unclaimed shares, or take the site over, but the change waits 72 hours. Every owner is emailed as soon as it's asked for, and the site's owner, or any owner added before the person who asked, can cancel it from the site page or the team tab. If nobody does, it lands. The credits source and the review queue stay with the site's owner; take the site over to change those.

In the review queue, a teammate can see what's pending, but only the owner can confirm or reject an article, because that sets who it pays.

Changing the payout wallet needs a fresh sign-in even for the owner, and it's recorded in the audit log.

If nobody can reach the account

If every owner has lost access, for example after a death, write to support from the email of the login that should take over. It needs a naulon login first. Two people on our team have to approve the request. We then email every current owner and wait seven days, and any of them can stop it by signing in and choosing Cancel change under Owners. If nobody does, the new login becomes an owner.

Working in more than one account

If you're on more than one team, or run your own account as well, the switcher at the top of the menu lists each organization with your role in it. Pick one and every page switches to that account's sites, earnings, billing and balance.

An organization doesn't need a site. A company that only buys creates one from the switcher, adds funds on its Buyer space and invites the people who will run its agents. Its Team page is in the Buyer menu as well, and someone who joins as a Developer or Analyst starts on the Buyer space, where their role does its work.

Connecting a site creates it in your own account. From inside someone else's, the Connect a site button isn't offered, so a site never ends up in the wrong place.

Inviting someone

Owner and Admin can invite. Pick a role (Admin, Billing manager, Analyst, or Developer) and enter an email. A Billing manager can move the organization's buyer balance, so only someone who can manage that balance may give the role, change it or remove someone who holds it; an Admin can't. No access exists until the invitee accepts.

How many teammates you can have depends on your plan; see /pricing. A pending invite takes a seat when you send it, and re-sending to someone still pending doesn't take a second one. If the account has an unpaid invoice, new invites are refused until it's paid (see Billing and invoices); nobody already on the team loses access.

What the invitee sees. The email link, after they sign in or create an account, opens a page naming your account and the role you offered. It only matches the exact address you invited, so someone signed in under another address has to switch. Pending invites also show as a banner at the top of their Settings page. Accepting grants the role immediately; declining removes the invite. A used or revoked link shows the same "not valid" message in both cases.

You can revoke a pending invite from the roster list until it's accepted.

Provisioning from your identity provider (SCIM)

naulon supports SCIM, so your directory can drive the roster. It's under Settings → Security on every plan. Only the account owner can set it up, because a SCIM token can rewrite the whole roster without any role check.

Mint the token, hand it and the base URL to your provider, and map each of its groups to a role. A group may map to any role except Owner, including any custom role you've defined. Your directory decides who's an employee; it never decides who owns the account.

The secret is shown once, when you mint it. The settings page can't reveal it again, and the audit log records only a short preview. Each account has one live token, so minting again rotates it and kills a leaked one.

The roster below the mapping shows who your provider has provisioned, pending rows included. A pending membership grants nothing until that person first signs in under the address the directory sent.

Changing a role

Owner and Admin can change anyone else's role, except an owner's, which isn't editable through this screen: owners are added and removed under Owners. A new role replaces the old one completely and immediately.

Removing a teammate

Owner and Admin can remove anyone who isn't an owner. Access ends immediately, and any agent token they were issued against the account's wallet is revoked in the same action.

Their author credit and payout wallet on your sites are untouched; remove those separately if you mean to. See For authors.