-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spaces in serverless #5813
base: main
Are you sure you want to change the base?
Spaces in serverless #5813
Conversation
A documentation preview will be available soon. Request a new doc build by commenting
If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here. |
🚀 Built elastic-dot-co-docs-preview-docs successfully!
|
Align across platforms, and omit "feature visibility" since it's unavailable in security
This link will be broken until elastic/docs-content#55 is merged
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left one question, otherwise 🚢 it
tags: [ 'serverless', 'security', 'reference' ] | ||
--- | ||
|
||
((elastic-sec)) supports the organization of your security operations into logical instances with the <DocLink slug="/serverless/spaces">spaces</DocLink> feature. Each space in ((kib)) represents a separate logical instance of ((elastic-sec)) in which detection rules, rule exceptions, value lists, alerts, Timelines, cases, and ((kib)) advanced settings are private to the space and accessible only by users that have role privileges to access the space. For details about configuring privileges for ((es)) and ((kib)), refer to <DocLink slug="/serverless/security/detections-requirements" section="detections-permissions-section" />. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bit confused why we're linking to detections requirements when the sentence is talking about ES and Kib.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it make sense to link here instead?
Contributes to https://github.com/elastic/security-docs-internal/issues/31. Also fixes #6019.
Preview
Note that we're no longer trying to omit "Kibana" from serverless docs, as that no longer seems to be a requirement (it's all over the UI). So this content mostly mirrors the ESS version in sometimes referring to spaces as "KIbana spaces," though in some instances this has been shortened to just "spaces" for simplicity.