Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 8 Current »

Power User

  • Delete, Rename, Update BIE owned by others

  • Delete, Rename, Update Published BIEs

    • For example, when reusing BIE. Even though still experimenting with BIE, it has to be published first to be reused. But later may need to modify or delete that BIE b/c it is not good enough yet.

  • Update State from Published to Candidate, Edit

Admin Role should be able to inactivate users, reassign BIEs from inactive user to another user

This page is the role from the Express pack perspective. /wiki/spaces/SWG/pages/793837626

Score 2.x Enhancement related to role-based access.

For End user on End User BIE

Note that BIE in the table below means end user BIE and includes end user code lists.

Role\Functionality

Read Production BIE

Copy BIE

Read & Copy non-Production BIE

Create/Edit BIE Not in Production State

Edit BIE in Production State

Express BIE (when in appropriate state and ownership)

Discard owned WIP BIE

Discard Production BIE, even unowned (orphaned BIE)

Transfer ownership when owned and in WIP state

Transfer ownership when not owned in any state

Uplifting BIE (that he can read)

Extend BIE globally

Public End User Role: Require login

Y (Maybe allow Architect End User to configure what BIEs are readable)

N

N

N

N

Y

N

N

N

N

N

N

Enterprise End User Role

Y

Y

Y

Y

N

Y

Y

N

Y

N

Y

N

Architect/Admin End User Role

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Y

Focus on the Enterprise End User and Architect End User Roles for now.

For End User on End User CC

Role\Functionality

Read CC in production

Read CC in non-production

Create/Edit CC Not in Production State

Amend CC

Delete owned WIP CC

Restore deleted CC

Purge deleted CC

Transfer ownership when owned and in WIP state

Transfer ownership when not owned in any state

Uplifting CC or code list (that he can read)

Namespace Management

Public End User Role: Require login

Y

N

N

N

N

N

N

N

N

N

Enterprise End User Role

Y

Y

Y

Y

Y

Y

N

Y

N

Y

Architect End User Role

Y

Y

Y

Y

Y

Y

Y

Y

Y

For End User on Developer/Standard BIE

Do we still need the notion of developer the BIE, because right now Express Packs are created by end user role? Developer users cannot have extension or use non-standard code list and EUCC.

Role\Functionality

Read & Copy Production BIE

Read & Copy non-Production BIE

Create/Edit BIE Not in Production State

Edit BIE in Production State

Express BIE (when in appropriate state and ownership)

Discard owned, WIP BIE

Discard Production BIE, even unowned

Transfer ownership when owned and in WIP state

Transfer ownership when not owned in any state

Uplifting BIE (that he can read)

Extend BIE globally

Public User Role: Require login

Y (Maybe allow Admin/Architect Developer to configure what BIEs are readable)

N

N

N

N

N

N

N

N

N

N

Enterprise End User Role

Y => copied BIE becomes end user’s BIE

N

N

N

Y

N

N

N

N

Y => uplifted BIE becomes end user’s BIE

N

Architect/Admin End User Role

Y => copied BIE becomes end user’s BIE

N

N

N

N

N

N

N

N

Y => uplifted BIE becomes end user’s BIE

N

For End User on Developer/Standard CC

All End users can only read developer CCs and BIEs as it is now.

Can end users can express the CC schemas.

Role\Functionality

Read Published CC

Read non-pubished CC (i.e., CC in Working branch)

Create/Edit CC Not in Published state

Revise CC

Delete owned WIP CC

Restore deleted CC

Purge deleted CC

Transfer ownership when owned and in WIP state

Transfer ownership when not owned in any state

Release Management

Module Management

CC Expression

Public End User Role: Require no login

N

N

N

N

N

N

N

N

N

N

Enterprise End User Role

Y

Y

Y

Y

Y

Y

N

Y

N

Y

Architect End User Role

Y

Y

Y

Y

Y

Y

Y

Y

Y

For Developer on Developer/Standard BIE

For Developer on Developer/Standard CC

For Developer on End User BIE and CC

Developers can only read end user BIEs and CCs as it is now.

Manage Account

Admin

  • No labels