Accounts, team and AI keys

Inviting people, what the two roles can do, adding an AI provider, turning it off, and reading ersASO from your own agent.

Inviting a colleague

Owners invite by e-mail address and role. The person gets a link and sets their own password; nobody else sees it or chooses it. Until they open the link they show as invited in the list and cannot sign in.

If e-mail delivery is not configured, the invitation link is shown on screen so you can pass it on yourself.

If the address is already in your workspace, you are told so. Any other address that cannot be invited gets one and the same message whatever the reason — ask the person to use a different e-mail address. Saying more would let the invite form reveal which addresses are registered elsewhere.

There are two roles. Owners manage the team, the plan and integrations. Members use the panel. The last owner cannot be removed or demoted, and nobody can remove their own account while they are the only owner.

AI is optional and it is your key

Pick Claude, Gemini or ChatGPT for the workspace and add that provider's key. It is stored encrypted and used only for your own requests. All three receive exactly the same instruction.

Your choice is not the last word: if the selected provider has no key but another one does, the call goes to the one that has a key. Otherwise a user who left Claude selected and pasted a Gemini key would see the feature as unavailable.

One switch turns AI off for the whole workspace. Turning it off does not delete your keys, and the AI-backed surfaces are simply not drawn — no dead buttons. Everything else works exactly as before: keyword discovery, scoring, rank tracking, the coverage matrix and the ASO score have never needed AI.

AI visibility

People increasingly ask a model which app to use instead of searching the store, and the name it gives back is a distribution channel of its own. A collapsed card on the app overview asks your provider which apps it would recommend for your strongest tracked keywords — in your app's own language and store region — and records whether it named you and which of your competitors it named.

The model is told nothing about your app: not its name, not its listing, not your competitors. Putting your name in the question would be answering it. Every need is one line of a single request, so a check costs one call on your own key, with a ten-minute cooldown per app.

A check is one observation, not a probability. A model answers differently from one day to the next, which is why the card never invents an "AI visibility score": it records the model that answered and the day, and builds up a tally as you run it again — named in three of five checks. That is the number to read. The competitor column is a tally over the window too, rather than the last answer alone: four of five checks named this rival.

Nothing is kept from the text of the answer, only the measurement. A need the model did not answer in a readable form is skipped rather than recorded as "did not name you" — not answering and not naming are different things.

Reading ersASO from your own AI agent (MCP)

If you work with an AI agent — Claude Code, Cursor or anything else that speaks MCP — it can read this workspace directly instead of you copying numbers out of the panel. Integrations has an MCP access card where an owner creates a key; the card also shows the server address to paste into the agent.

Five tools are published: the app list, the keyword pool with popularity, difficulty, relevance and your position, the daily rank history of one keyword, the keyword gaps against your competitors, and the listing audit with every check. Ask your agent for the apps first — every other tool needs the app id that comes back.

Everything is read-only. An agent cannot add keywords, start a measurement, change your listing or touch a setting, and no tool sends a request to Google Play — the answers come from measurements that were already taken. This is deliberate: an agent looping over a write endpoint would burn a daily Play budget that cannot be refunded.

The tools tell the agent the same thing the panel tells you: popularity and difficulty are estimates derived from public store signals, and a missing score means the value could not be measured, never zero. A model that is not told this reads those numbers as more certain than they are.

• The key is shown once, at creation. Only its hash is stored, so a lost key is replaced rather than recovered.
• Each key is revoked on its own and the list shows when each one was last used, so a key you no longer recognise is easy to spot.
• A key belongs to the workspace, not to the person who made it, and it reads everything the workspace can see. That is why only owners can create one.

Limits

Limits are enforced when you add something, never by cutting what you already have. If a limit is lowered, what you already track stays; you just cannot add more.

The keyword limit is a total across the workspace, not per app, because that is what actually costs: every tracked keyword is re-measured, most of them every night. Competitor limits are per app.

The Keywords page and the add-app wizard both show how much of the plan you have used. Those numbers come from the same queries that accept or refuse an addition, so the counter never offers room the server will then refuse.

New workspaces start on the Free plan. Paid plans are set up by e-mail for now: write to info@ersaso.com and we will switch your workspace over — the warning in the add-app wizard points at the same address.

Separately from the plan, a few expensive actions have an hourly ceiling per workspace; the numbers are in How measurement works.

Your account

Password changes sign out your other sessions but keep the tab you are working in. A password reset signs out everything, without exception — someone resetting a password is usually taking an account back.

A card on the same page, collapsed by default, lists where you are signed in: when each session signed in, when it was last seen, its IP address and the browser it reported, with the one you are using marked. A single button ends all the others. Sessions are stored server-side and survive a release, so the list stays accurate; it still shows what is open right now, not a history of your devices, because a session drops off when it is signed out or expires. A session that sees no activity for seven days expires on its own.

Deleting your own account leaves the workspace to the other owners. Deleting the workspace removes everything for everyone; both ask for your password first.

Two-step verification

Optional, per person, on the Accounts page. Once it is on, signing in asks for your password and then a 6-digit code from an authenticator app — Google Authenticator, 1Password, Authy or any app that reads the standard QR code.

1. Open Accounts and choose Set up under Two-step verification.
2. Scan the QR code with your authenticator app, or type the setup key by hand.
3. Enter the code the app shows and your current password, then choose Turn on.
4. Save the ten recovery codes that appear. They are shown once; download or copy them before you close the box.

A recovery code signs you in once if you lose your phone; each works a single time and the page shows how many you have left. New recovery codes replace the old ones. Turning the feature off, or creating new codes, asks for your password and a current code.

A code works once: the same code cannot be used for a second sign-in, and wrong codes count toward the same sign-in lock as wrong passwords. If you lose both your phone and your recovery codes, write to info@ersaso.com from your account's e-mail address; the second step can be removed after we confirm it is you.

Interface language

The panel follows your browser's language until you pick one. The selector sits at the bottom of the sidebar, just above your e-mail address, and on the sign-in page before you have an account. English and Turkish are available; each language is listed by its own name.

The choice is per person and is saved to your account, so it follows you to other devices. E-mails use it too: sign-in links, alerts and the weekly summary arrive in the language of the person who receives them. An alert address that does not belong to a member of the workspace gets the language of the workspace owner.

Interface language is not the language of your listing. Keyword matching, stop-words and harvest always use the listing's own language, whatever you read the panel in.