Application Owner:
For each application, there can only be one assigned owner.
The application owner has the highest level of access and permissions within the Algolia dashboard. They have the authority to manage team member access and permissions, billing information, access to API keys of all team members etc.
Being an account owner comes with the responsibilities of overseeing and maintaining the Algolia account and associated applications.
Best Practices for the Application Owner:
- Use a shared entity/company email address rather than an individual email for the owner of your Algolia application/s. If you’re using an individual's email address as the account owner, your team might lose access if this person leaves the company or becomes unavailable. You could then potentially lose access to the application and associated API keys required for security verification to recover the account and associated applications.
- Our team recommend only using the API keys of the application owner in your production app. This is because the owner's API keys are never deleted (unless you manually delete them yourself).
- You can read more on our Security best practices here.
Team members:
The application owner or any team member with “team” permissions can configure team member access to your Algolia applications through the Team Management page.
You can get to this page by clicking on your profile at the bottom of your dashboard sidebar, and then clicking the Team button.
To add users to your application, use the Add Team Member button at the top right of the Team page. Enter the user email and select the application(s) (and optionally specific indices) you want to give them access to.
There are six permission sections, each with subcategories that allow for more granularity:
- Set-up Search: whether your team member can add records and configure index settings.
- View Search: whether your team member can use the dashboard search page and view index settings.
- Billing: whether your team member can see billing information.
- Features: whether your team member can view and configure special features like A/B testing, Query Suggestions, Analytics, etc.
- Team: whether your team member can add new team members and view team member permissions.
- Crawler: whether your team member can view or configure the Crawler.
- Other: whether your team member can view and edit API keys.
Parent/Child Configuration:
Only eligible plans can configure a parent/child relationship between applications - This is currently limited to our Premium and Elevate committed plans.
The standard behaviour of an application is to have a singular quota and generate its own invoices.
For example, a user who owns three applications will receive three invoices, each reflecting the individual applications consumed usage.
When a Parent-child relationship has been configured between applications it allows for the usage of several applications to be aggregated towards one committed quota which is then billed on a single invoice/contract.
- The contracted application is known as the “Parent” and any applications tied to this same contract/quota are known as the “Child” applications.
- All applications in the parent/child configuration must be owned by the same account.
If you would like to configure a Parent/Child relationship between your applications or speak with a member of our sales team regarding the premium plan options, please contact the support team directly via the Support Portal