Module role limitations

The following table describes the limitations of possible module roles in detail.

Module Role	Description	Effects (yambas)	Effects (dashboard)
DEPLOY	The owner of the module or Customer who can modify the module, including classes and code, and in addition has the right to deploy the module	Rights of WRITE, plus: Can deploy module	classEditor Rights of WRITE, plus: can deploy
WRITE	Customer who can modify the module, including classes and code	Rights of READ, plus: Can create classes or attributes Can modify ServerCode Can modify NativeModule code Can delete module	classEditor can add, edit and remove metaModels of module can add, edit and remove attributes of metaModel can download and upload native Modules from MyModules data rights depend on Application Role
READ	Customer who can use a module, but not modify it	See and use the module, even if unreleased	classEditor can not add, edit and remove metaModels of module can not add, edit and remove attributes of metaModel can not download and upload native Modules from MyModules data rights depend on Application Role

Note:

Static Modules like Facebook, Twitter or Basic Module have no special rights. Every Customer has READ rights for them.
Non static and non Native Modules ( for example: ...Main) can have rights (see table above)
Native Modules (for example: SAP) can have rights (see table above)