Context:
When solving use cases related to multiple B2B customers, as Orders in Commerce or Customer Portal use cases, the ownership of the data must belong to the company account. Having the ownership defined by account, means that only users with access to that account can access its data. This can happen via users that belong to those accounts or managers of the accounts through Liferay Organizations related to that specific account.
Design deliverables:
Acceptance Criteria
1 - Given an objects admin,
when adding a new Objects,
then I should be able to define that a user can only see entries from an account that they are part of
2 - Given an objects admin,
when adding a new entry in an object that has restriction by accounts,
then the accounts selector should be mandatory
3 - Given an account member,
when adding a new enty in a objects scoped by account
then I should be able to only add entries to the accounts that I have access to
Definition of Done (DoD):
- All Acceptance Criteria were passed;
- Make sure that the expected automated tests were created (unit / integration / functional) and passed successfully;
- Validated by QA and Product Manager;
- No critical bug related to Story scope (FP5);
- Make sure that all system documentation were updated (if necessary)
- depends on
-
LPS-150954 Investigate Data Restriction (Accounts, Organization, ...)
-
- Closed
-
-
LPS-153768 Migrate Object to use more DB and less ES
-
- Closed
-
-
LPS-154197 Data Restriction by Accounts POC
-
- Closed
-
- is a dependency of
-
LPS-152172 Remove FF of restrict data by accounts
-
- Closed
-
-
LPS-157205 Remove FF of restrict data by accounts
-
- Closed
-
-
LRDOCS-10478 Document Restrict Data From Accounts
-
- Merged For Publication
-
- relates
-
LPS-155962 As a power user, I want to allow users to manage data scoped by accounts
-
- Closed
-
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...