Reconciles the Roles page

[yetanothertw]

The Roles page is duplicated and exists in both the Deploy and manage and the Reference sections. The content is starting to drift, so I'm editing the page in the Reference section to reconcile the information.

Refers to #2738

Details:

• The kibana_user role is deprecated, so I added the applies_to tag. I can't find info on when it was deprecated only that it is deprecated.
• The kibana_dashboard_only_user is deprecated, so I added the applies_to tag. I can't find info on when it is deprecated (strange I can find no mention of this role in the Kibana repo).
• The reporting_user roles is marked as deprecated here but wasn't marked as such on the Roles page in the Reference section, so I've updated that.

[github-actions]

🔍 Preview links for changed docs

• docs/reference/elasticsearch/roles.md

[elasticsearchmachine]

Pinging @elastic/core-docs (Team:Docs)

[shainaraskas]

shocking that there are so few deprecated roles - works for me.

couple of little comments then good to go

[shainaraskas]

no need to clarify "if you're using stack" here because the page is labeled as stack and serverless has different built-in roles

if you really felt fancy you could add a note to that effect (details here)

[yetanothertw]

Thing is I wanted to include another link to info about roles in Serverless (similar to what we did in the privileges page), and then I forgot to get back to that paragraph and add the link.

Do you think it works now, @shainaraskas ?
I've isolated it in a tip because it only slightly relates to the content on the page, but could be very useful to someone who landed on that page accidentally and was looking for directions on how to get to the Deploy and manage section.

[shainaraskas]

I think that the way that this is organized together in a single tip is confusing. one of the paragraphs is explaining more about applying the roles that you're reading about now, and the other is redirecting you to a different location if your context is different.

I've provided a couple of edits that I think addresses the confusion.

In general, I think redirections make sense in a note, but information that is key to applying or understanding a concept should not.

[yetanothertw]

Thank you for expanding on that, it makes a lot of sense. I think it's good guidance and we should have it documented somewhere, because the way we link to other docs is not consistent and it's difficult to infer what the recommended patterns are.

[github-actions]

ℹ️ Important: Docs version tagging

👋 Thanks for updating the docs! Just a friendly reminder that our docs are now cumulative. This means all 9.x versions are documented on the same page and published off of the main branch, instead of creating separate pages for each minor version.

We use applies_to tags to mark version-specific features and changes.

Expand for a quick overview

When to use applies_to tags:

✅ At the page level to indicate which products/deployments the content applies to (mandatory)
✅ When features change state (e.g. preview, ga) in a specific version
✅ When availability differs across deployments and environments

What NOT to do:

❌ Don't remove or replace information that applies to an older version
❌ Don't add new information that applies to a specific version without an applies_to tag
❌ Don't forget that applies_to tags can be used at the page, section, and inline level

🤔 Need help?

• Check out the cumulative docs guidelines
• Reach out in the #docs Slack channel

[shainaraskas]

I think that the way that this is organized together in a single tip is confusing. one of the paragraphs is explaining more about applying the roles that you're reading about now, and the other is redirecting you to a different location if your context is different.

I've provided a couple of edits that I think addresses the confusion.

In general, I think redirections make sense in a note, but information that is key to applying or understanding a concept should not.