01
Enable and hire the teammate
An Opal administrator first enables the Virtual Teammate for the organization. A permitted user can then open the Virtual Teammates directory, choose the role and hire it.
- If the directory shows Request rather than Hire, administrator enablement is still required.
- Give the teammate a clear name and role purpose.
- Treat the virtual identity like a new worker account with scoped responsibilities.
02
Choose instances and grant access separately
Choosing an Optimizely product instance tells the teammate where to work; it does not grant the necessary permissions. Roles in Opti ID Admin Center and, for CMS, content-level rights may still need configuration.
- Use least privilege.
- Grant only the product and content actions needed for current jobs.
- Review access again before expanding autonomy.
03
Connect third-party tools
A human must authorize external systems such as GA4, Search Console or HubSpot on the teammate's behalf. Role-specific teammates require different connectors.
- Verify the connected property or account is the intended one.
- Do not give a broad administrator account simply because setup is faster.
- Document who owns each external connection and how it can be revoked.
04
Commission with approval first
Optimizely's default model begins with proposed work and human approval. Test one job end to end, inspect the output and only then consider allowing narrow actions to run automatically.
- For SEO, start with a briefing or audit rather than production edits.
- For CRO, start with analysis or draft experiment configuration.
- Review upcoming jobs, past runs, interactions, connectors and permissions regularly.
Sources
Primary and supporting sources
Facts were rechecked against the linked sources immediately before publication. Pricing, product availability and rollout status can change.