What can manager sub-accounts do
Manager sub-users have the opportunity not only to view, but also to edit main project settings, including:
- add/delete keywords;
- choose search engines for analysis;
- change the check frequency
- change the search check depth
- edit the order of projects or keyword groups;
- export project data;
- add projects (if allowed by the administrator);
- delete projects (including projects created by other sub-users and administrator)
Sub-account users (including client account users) don’t have access to the “Subscription” and “Get Bonus” sections.
All the changes that sub-users can make to projects relate primarily to the Rank Tracker tool. You can provide access to other modules as you deem appropriate. All these settings are available during sub-account creation and for existing accounts.
Under sub-user profile settings, you can change the password, language, give access to necessary sections and tools, set account and budget limits or change the status of the account to "the client".
What can client sub-accounts do
Client sub-users can view projects, but cannot edit the settings, update rankings, change the order of projects or groups, nor add/delete projects. For client sub-accounts, the administrator can grant access to particular sections and tools, as well as hide the column with the keyword volume in the rankings table. All these settings are available during sub-account creation and for existing accounts. Client sub-account users can export data from the available sections.
What sub-accounts can and cannot access
Sub-account access is permission-based. The editing rights described above are centered on the Rank Tracker tool by default, but the administrator can grant sub-accounts access to many other product areas — including reporting, analytics and traffic, competitor research, audit and monitoring, backlinks, keyword and SEO tools, content tools, local marketing, social features, insights, and newer AI-related areas.
What sub-accounts generally cannot access are the main account’s administrative and commercial areas — such as subscriptions, purchases, payments, invoices, contracts, certificates, and wallet/top-up flows, along with some account-level integrations and support tooling. Sub-accounts also do not automatically see other sub-accounts’ data: outside their own scope, access depends on explicit sharing plus the required project permissions.
Can a sub-account view reports created by other sub-accounts or the main account?
Report visibility is not automatic across accounts. A report becomes visible to another account only when it is explicitly shared, and sharing is limited to accounts under the same main account. In addition, the recipient must already have access to the projects included in the report. Shared reports can be opened by the recipient, but non-owners do not get full owner control over them.
Can a sub-account have its own API key?
It depends on which API is used. The legacy API does not support sub-accounts, so access there is blocked. The newer API dashboard and key-management flow is permission-based: if a sub-account has the required API / Data API entitlement, it can be granted API access and manage its own keys in that newer flow.
Can sub-accounts authorize connectors (e.g. Google Analytics / Google Search Console)?
Google Analytics / Google Search Console connections are supported for sub-accounts, with some limits. Manager-type sub-accounts can authorize their own connection when they have the relevant permission, and that connection is stored under the sub-account that authorized it. The main (parent) account can access a sub-account’s Google connection, but the reverse is not true — a sub-account cannot manage a connection owned by the parent as if it were its own. Client-type sub-accounts are more restricted and are blocked from direct Google token management.