Getting started with elba

Start with the foundation

elba brings together identity, SaaS, browser, data-protection, and employee security context. A deliberate setup order helps your team establish useful coverage before adding more integrations and workflows.

If your workspace has not been configured yet, begin with Onboarding.

1. Review your workspace and users

Confirm that your organization name and logo are correct, then review the users imported from your identity provider.

Use Members to decide who should be enrolled in elba and how new users should be handled. Assign additional administrators only to people who need workspace-level access; see Admins.

2. Connect your priority applications

Connect the applications that hold your most important identity and security context first. The available data differs by application, so review Integration capabilities before selecting the initial set.

Follow Connect an integration for the connection flow. After connecting an application, confirm that its users and expected security data appear before moving to the next one.

3. Review the first security findings

Use the dashboard to understand the initial risk picture across your connected applications.

Useful starting points include:

• Third-party apps for reviewing external application access.
• Data protection for sensitive information found in connected services.
• Employee risk profile for investigating risk in user context.

Prioritize a small set of meaningful findings and confirm ownership before expanding your scope.

4. Add browser visibility

Use the Browser extension to add browser-level context to your elba workspace. Start with a representative pilot group, validate installation and sign-in, and then expand the rollout using Deploy the browser extension.

Review Browser extension capabilities to decide which browser signals are relevant to your security program.

5. Configure communication

Choose the communication channels and preferences that fit your organization. Clear ownership and purposeful notifications help administrators respond without creating unnecessary noise.

If employees will receive requests or guidance through elba, explain what they should expect before enabling a broad rollout.

6. Introduce automated workflows

Playbooks help turn repeatable security decisions into consistent workflows. Start with a narrow, well-understood use case, review the configured conditions and actions, and validate the outcome with a limited scope before expanding it.

Keep a clear owner and rollback approach for every workflow that can change user or application state.

7. Build employee engagement

Once the workspace foundation is in place, select the employee security programs that match your goals:

• Training for security learning programs.
• Phishing for phishing awareness exercises.
• Sam for employee-facing security guidance in supported communication channels.
• Security leaderboard for visibility into team participation and progress.

Introduce these programs with clear communication, defined ownership, and an initial audience that can provide feedback.

Ongoing operating checklist

• Review new users and administrator access.
• Confirm that important integrations continue to report expected data.
• Triage high-priority findings and assign owners.
• Monitor browser extension deployment status.
• Review automated workflow outcomes and adjust their scope when needed.
• Keep employee communications and learning programs current.
• Revisit Trust and security and Compliance when preparing customer or audit evidence.

If something is not behaving as expected, start with Troubleshooting.