Notes - Permissions and public notes #243
Description
Rationale
1. Functional Requirements
Top User Stories
Share option
When selecting the options "Selected space" and "Current space", I have a complementary option section "Share" with the option "Make it public".
When the activate the option, all the notes selected have automatically the access "public".
All people who can have access to the page where the portlet is displayed can know see the notes.
Permission note
Permission drawer
Given I'm a space/admin, space/publisher or space/redactor
Then I have an option "Manage access" on the action menu. It opens a new drawer "Note persmission" with the name of the note.
Note owner
I have the user who initially create the note. The owner will always have an access to this note.
Space permissions
I have a first tab "Space permissions" to manage all the permissions related to space members.
I have 2 roles:
- members
- space admins, redactors and publishers
For each role, I can activate or deactivate the permissions. There are 2 permissions:
- View: to be able to see, navigate between the notes, print to pdf, bookmark, open history version, copy link, export
- Edit: to be able to create, edit, delete, move, import, restore a version, duplicate
NB: the publication permissions are linked to the roles and are not displayed in this menu.
I can click on the permission title to open an additional drawer with the definition of the permissions.
It's not possible to deactivate the permission for the role "space admins, redactors and publishers". On hovering over it I have a tooltip "You cannot deactivate this permissions".
Share options
Share with other users
Public links
Consult a public note thanks to a link
Impacts
Gamification
Notifications
Analytics
We need to be able to track the public view on the notes. For "View content", we need to be able to track view from public page (notes or news).
Unified Search
2. Technical Requirements
Expected Volume & Performance
Security
Extensibility
Configurability
Upgradability
Existing Features
Feature Flags
| Property Name | Default Value | Target Audience | Functional Behaviour |
|---|---|---|---|
Other Non Functional Requirements
3. Impacts
Documentation
Training
4. Software Architecture
Security
Access
- GUI
- API
Services & processing
- Ex: Scheduled Jobs
Data and persistence
- Macro data model
- Persistence layer
- Use of caches
Clustering
Multitenancy
Integrations
Migration strategy
5. Annexes
- Reasoning that explain the technical choices
- Impacts
- References