Profiles overview

Elastic profiles extend the Opsflw Connect profile system to observability data. They map tenant requirements to index lifecycle policies, role mappings, and curated dashboards so teams can grant least-privilege access quickly.

What profiles configure

• Data views specify index patterns, default time ranges, and filters for dashboards.
• Role mappings align tenant SSO groups with Elastic roles that control read and write permissions.
• Lifecycle policies enforce retention and rollover schedules that match compliance obligations.

Each profile references a baseline set of Kibana objects stored in Git, ensuring reproducible dashboards across environments.

Workflow for updates

1. Clone the Elastic content repository and create a feature branch for the profile change.
2. Update the JSON exports or Fleet packages that define dashboards and visualizations.
3. Submit a pull request with screenshots, retention impact, and expected migration steps.

Automation syncs merged changes into staging first, then production during the next maintenance window.

Validation checklist

• Confirm role mappings continue to enforce least privilege with automated access tests.
• Verify dashboards load within SLO targets after the sync completes.
• Ensure lifecycle policies keep storage costs within the allocated budget by reviewing hot and warm usage.