With our multi-user feature, you can create and manage a team, giving them access to various aspects of your WordPress websites, applications, or databases. We offer a number of roles to allow you to fine-tune user access. This article explains the various capabilities you can give to your users.
Company Ownership Role
There is a special role called the Company Owner. A Company Owner is always also a Company Administrator. There can only be one Company Owner per company.
A Company Owner is the only user in a company who can request an account closure or transfer company ownership (to a Company Administrator in the same account). Apart from that, they are exactly like Company Administrators in day-to-day use.
Managed WordPress Hosting
When inviting or modifying a user, the first choice is to give the user Company access or WordPress site access. Site-level users only have access to specific WordPress sites you assign to them, while company users see company-level details. There are 3 company-level and 2 site-level user roles to choose from, with various levels of access based on their role.
All user roles have access to Kinsta’s Support team, but we can only assist with sites your user role can access.
Company Administrator
Company Administrators have the highest level of access. They have complete control of all company and site data, including DNS in MyKinsta and migration requests. Only give Company Administrator access to users who you trust.
Company Developer
A Company Developer has access to manage all sites and DNS in MyKinsta and can manage site-level users. They can also delete sites that do not have a Premium Staging Environment add-on. They do not see billing details, company settings, or migration requests. While a Company Developer can view the list of company users (including email addresses and roles), they cannot make any changes to company-level users.
Company Billing
A Company Billing user is a special role that only sees billing details and company settings. They can see invoices, enable automatic invoice emails, and modify company details like name and address. They do not have access to any websites or migrations in any way.
WordPress Site Administrator
WordPress Site Administrators have complete access to a site and have control of all environments attached to that site. The only actions they are not permitted to do are removing a site from a company’s account, submitting or managing migration requests, accessing DNS in MyKinsta, or creating and deleting Premium Staging Environments. Note that a single user may be a WordPress Site Administrator for multiple sites.
WordPress Site Developer
WordPress Site Developers have access to the staging environments for the site(s) they are given access to. They only have control over the staging environments and can perform most actions apart from removing the staging environment or pushing it to live. Note that a single user may be a WordPress Site Developer for multiple sites.
WordPress Site Developers do not have access to company-level or live environment analytics, user management, migrations, DNS in MyKinsta, or the company-level activity log in MyKinsta. They cannot create or delete Premium Staging Environments.
MyKinsta User Roles and Permissions Chart
The following chart provides more specific details about the capabilities each user role has.
Capability | Company Owner | Company Administrator | Company Developer | Company Billing | WordPress Site Administrator | WordPress Site Developer |
---|---|---|---|---|---|---|
Access billing details or change plan | Yes | Yes | No | Yes | No | No |
Access referrals | Yes | Yes | No | Yes | No | No |
Cancel plan | Yes | No | No | No | No | No |
Access company analytics | Yes | Yes | Yes | No | No | No |
Manage all sites | Yes | Yes | Yes | No | No | No |
Manage 1 site | Yes | Yes | Yes | No | Yes | No |
Install or remove a paid add-on | Yes | Yes | No | Yes* | No | No |
Approve inbound site transfer | Yes | Yes | No | No | No | No |
Initiate inbound site/DNS transfer | Yes | Yes | No | No | No | No |
Request paid malware cleanup** | Yes | Yes | No | No | No | No |
Request a data center change | Yes | Yes | Yes | No | Yes | No |
Request a site migration | Yes | Yes | No | No | No | No |
Manage site labels | Yes | Yes | Yes | No | Yes | No |
Request 2FA be disabled for other users in a company*** | Yes | No | No | No | No | No |
DNS in MyKinsta | Yes | Yes | Yes | No | No | No |
Add or delete site/live environment | Yes | Yes | Yes**** | No | No | No |
Access live environment | Yes | Yes | Yes | No | Yes | No |
Access live environment analytics | Yes | Yes | Yes | No | Yes | No |
Access or Add Standard Staging Environment | Yes | Yes | Yes | No | Yes | Yes |
Delete Standard Staging Environment | Yes | Yes | Yes | No | Yes | No |
Add or delete Premium Staging Environment | Yes | Yes | No | No | No | No |
Access Premium Staging Environment | Yes | Yes | Yes | No | Yes | Yes |
Access any staging environment analytics | Yes | Yes | Yes | No | Yes | Yes |
Push any staging to live | Yes | Yes | Yes | No | Yes | No |
Push any staging to another staging | Yes | Yes | Yes | No | Yes | Yes |
*Can add a disk space add-on but cannot manage hourly or external backups; those are managed at the site level.
**If the malware cleanup is free, any user can request it.
***Can request this if the user is only in one company.
****Can delete a live environment if no Premium Staging Environment is attached to it.
Application and Database Hosting
With Application Hosting and Database Hosting, you can choose between 3 company-level user roles with various levels of access based on their role.
All user roles have access to Kinsta’s Support team, but we can only assist with applications or databases your user role can access.
Company Administrator
Company Administrators have the highest level of access. They have complete control of all company details and application and database settings. Only give Company Administrator access to users who you trust.
Company Developer
Company Developers can access all application and database settings but do not have access to create or modify billing events. The following actions are billing events in Application and Database Hosting, which means a company developer does not have access to them:
- Add or remove applications or databases.
- Change the build resources for an application.
- Change the pod size or the number of instances for an application process.
- Change the database size.
- Add or remove a database disk space add-on.
If you want a Company Developer to have access to create and remove applications, you must increase their access level to Company Administrator.
Company Billing
A Company Billing user is a special role that only sees billing details and company settings. They can see invoices, enable automatic invoice emails, and modify company details like name and address. They do not have access to any applications or databases in any way.
MyKinsta User Roles and Permissions Chart
The following chart provides more specific details about the capabilities each user role has.
Capability | Company Owner | Company Administrator | Company Developer | Company Billing |
---|---|---|---|---|
Access billing details or change plan | Yes | Yes | No | Yes |
Access referrals | Yes | Yes | No | Yes |
Add applications or databases | Yes | Yes | No | No |
Manage applications or databases | Yes | Yes | Yes* | No |
Delete applications or databases | Yes | Yes | No | No |
Access company analytics | Yes | Yes | Yes | No |
Access application and database analytics | Yes | Yes | No | No |
*Can only make changes that do not affect billing.