Space Settings & Roles

[srenault-meeds]

Rationale

We have, few weeks agos, allowed current space host to edit navigation and layout of their space.
This implies hosts knowing what they are doing.

In addition to that, permissions of spaces roles are not well understood by users, specifically the space host.
AND some permissions are too sensitive: space host can delete the space without knowing what they are doing.

Furthermore, the space banner is only editable from the stream. Problems are:

• Users mix this with image banner. Result is not the same. Space Banner is reminded in the spaces directory, in the search card of spaces
• Users can remove it from the layout. To edit it, you need to put it back available only on the stream page
• Users can update settings of the space from the related app excluding the space banner. Which makes the UX not consistent.

Thus, we propose by this MIP to enhance space settings for consistency and for UX sakes.

1. Functional Requirements

Top User Stories

Overview Settings
From the space settings, I can customize my space in few clicks, including the space banner.
That means that the space banner is no more provided in the space home layout. It is replaced by an image portlet
AND the space banner is no more suggested in the portlet catalog/registry when editing layout

Access & Visibility
From the space settings, I can setup access & visibility from a dedicated option.

Roles
From the space settings, I can view roles currently used in the space with their description and users.

When needed I can click to the list of users. From there, I am able to:

• filter the list
• remove users from the role
• add new user from the space members
• ONLY for members list, option to invite people to join the space

Adding user as admin:

In order to centralize the roles management, setting users as publisher or redactors will be only possible from this roles management. Hence, options from the members app will be removed.
Indeed, these roles need to be explicited and the better location for that is the space settings.

Thus, to make the space as a "redactional" one, the admin will have to enable the option.

When doing so, a drawer opens to explain the purpose of the Content Creation Restriction. Moreover, publishers previously identified are listed so you can understand they are identified as redactors and you can remove this role for some publisher.
If no publisher, a placeholder is proposed.

Precision: Roles will be updated as follow.

• Space host will be renamed as space admin (using Crowdin)
• Space Publisher will be able to write even when a redactor is identified
• Redactor role can be removed to publishers if needed

-> The user who creates a space becomes a "Space Administrator", he can invite other members and promote them to be admin or managers or redactors
-> The space cannot have no space admin.

Impacts

Gamification

--

Notifications

--

Analytics

--

Unified Search

NA

2. Technical Requirements

Expected Volume & Performance

No change on stored data. The performances shouldn't be affected as well by the roles modifications.

Security

The Space Roles checks (ACL) has to be centralized in a dedicated API which has to be reused everywhere.

Extensibility

The possible actions associated to each role has to be extensible using extensionRegistry mechanism as made in all other extensible UI component in the platform.

Configurability

Default Space Template Banner has to remain, but the default space home page configuration has to change in predefined Crowd Funding Space template to use an Image portlet instead of Space Banner

Upgradability

No data upgrade will be necessary, since the old Space Layout should remain as is by using the deprecated Space Banner portlet. Whereas, the Space Banner portlet instance should be deleted from portlet instances list.

Feature Flags

N/A

3. Software Architecture

Security

All existing spaces permission checks, has to rely on this centralized points, thus a deep code cleanup has to be made to not copy/paste the algorithm of ACL but reuse the one defined and centralized in SpaceService API.

Access

The Space Settings has to keep its extensibility to let other sections to be added into it.
Besides, the Space invitation UI has to be reusable to use the same UI & UX from Space Members and Space Settings.

[srenault-meeds]

To check please @margondicco

[margondicco]

Hello Go fonc thank you

[boubaker]

Ready for spec tech review by DAO Members (eXo : @rdenarie )