Understanding how application ownership, team permissions, and account structure work in Algolia is essential for managing access, security, and billing across your applications.
Application Owner
Each Algolia application has one assigned owner.
The application owner has the highest level of access, including the ability to:
- Manage team members and their permissions
- Access and manage billing information
- View and manage all API keys
- Oversee overall application configuration
This role also carries responsibility for maintaining access and ensuring the security of the account.
Best practices
- Use a shared company email address (e.g. team@company.com) as the application owner, rather than an individual’s email. This helps prevent access issues if a team member leaves or becomes unavailable.
- Avoid losing access to critical resources such as API keys required for account recovery.
- Use the application owner’s API keys in production, as these keys are not deleted unless manually removed.
For more information, refer to Algolia’s security best practices documentation.
Team Members
Team members can be added and managed by the application owner or any user with Team permissions.
To manage team access:
- Open your Algolia Dashboard
- Click your profile icon in the sidebar
- Select Team to access the Team Management page
To add a new user:
- Click Add Team Member
- Enter their email address
- Assign access to specific applications (and optionally indices)
- Configure permissions based on their role
Permission categories
Permissions are grouped into the following sections:
- Set-up Search: Add records and configure index settings
- View Search: View search results and index configuration
- Billing: Access billing and usage information
- Features: Use tools like A/B testing, Query Suggestions, and Analytics
- Team: Manage team members and permissions
- Crawler: Access and configure the crawler
- Other: View and manage API keys
These categories allow fine-grained control over what each team member can access and modify.
Parent/Child Application Configuration
On eligible plans (currently Premium committed plans), you can group multiple applications under a single contract using a Parent/Child configuration.
Default behavior
By default, each application:
- Has its own usage quota
- Generates its own invoice
For example, three applications would result in three separate invoices.
Parent/Child setup
With a Parent/Child configuration:
- Multiple applications share a single committed quota
- Usage is aggregated across all applications
- Billing is consolidated into one invoice
In this setup:
- The Parent application is tied to the contract
- The Child applications share the same quota and billing
Requirements
- Available only on eligible plans (e.g. Premium)
- All applications must be owned by the same account
To configure this setup or explore plan options, contact Algolia Support via the Support Portal.