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 3 Next »

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 and End User BIE

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

Role\Functionality

Read BIE

Create/Edit BIE Not in Production State

Edit BIE in Production State

Express BIE (when in appropriate state and ownership)

Delete Production BIE

Transfer ownership when owned and in WIP state

Transfer ownership when not owned in any state

Uplifting BIE (that he can read)

Public End User Role: Require no login

Read all BIE in certain release or Read certain BIEs in any release, etc.?

N

N

N

N

N

N

End User Role

Y

Y

N

Y

N

Y

N

Y

Architect End User Role

Y

Y

Y

Y

Y (even he does not own)

Y

Y

Y

For End User and End User CC

Role\Functionality

Read CC

Create/Edit BIE Not in Production State

Edit BIE in Production State

Express BIE (when in appropriate state and ownership)

Delete Production BIE

Transfer ownership when owned and in WIP state

Transfer ownership when not owned in any state

Uplifting BIE that he can read

Public End User Role: Require no login

Y

N

N

N

N

N

N

End User Role

Y

Y

N

Y

N

Y

N

Y

Architect End User Role

Y

Y

Y

Y

Y (even he does not own)

Y

Y

Y

  • No labels