Arize supports service keys which are designed for automated services and applications that need to persist beyond individual users. Service keys are tied to bot users rather than human users, ensuring they continue to work even if the original creator leaves the organization. Admins and Members can create service keys with permissions equal to or below their own access level.
If an Admin creates a service key for a data ingestion service that only needs access to Space A, the service key can be restricted to just that space—even if the Admin has access to multiple spaces. This follows the principle of least privilege for automated systems.