Skip to content
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

Update the security overview docs #8958

Open
wants to merge 3 commits into
base: development
Choose a base branch
from

Conversation

EnasAbdelrazek
Copy link
Contributor

For 10.20:

  • Document the Page, Nanoflow, microflow access tabs
  • Document the Export to Excel functionality

@WimJongeneel
Copy link
Contributor

Screenshot does still have the old export icon

@EnasAbdelrazek
Copy link
Contributor Author

@WimJongeneel Could you please update the screenshot?

5. Kind: Specifies whether the member is an association or an attribute.
6. Type: The type of the member.
7. XPath: The XPath constraint.
8. XPath Caption: The XPath constraint caption if exists.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

" if exists" feels a bit strange, maybe something like ", when set"?

6. Type: The type of the member.
7. XPath: The XPath constraint.
8. XPath Caption: The XPath constraint caption if exists.
9. Access: The member access right (None, Read, ReadWrite).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"access level" might sound nicer then "member access right"

9. Access: The member access right (None, Read, ReadWrite).

2. Document Access: This sheet includes the accessible pages, microflows and nanoflows, including:
1. Document type: The type of the accessible document (Page, Microflow, Nanoflow).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know if we should document that this (and some other) fields are translated and will be different based on your SP language.

Copy link
Contributor Author

@EnasAbdelrazek EnasAbdelrazek Jan 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

True, But that applies for everything in docs :)

3. Module: The module containing the the page, nanoflow, or microflow.
4. Document: The name of the page, nanoflow, or microflow.

3. Module Roles: This sheet provides the mappings between user roles and module roles in each module, including:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think "in each module" is relevant here, it is just all mappings

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants