Changes

In {{UBIK}}, an account object is called [[Login]], with the system [[MetaClass]] ''LOGIN''. Theoretically, a user can have multiple such login credentials, but normally, you'd have one per user. If there are multiple logins for one user, you can create a custom meta class for the users and link the login objects to them via [[Relation]] or the ''CONSUMER'' [[Reference]] property (see also how to [[HowTo:Relate_Objects]]). You can also create a derivation of the ''LOGIN'' system meta class to add further details for the instances.A login object has the following important properties:* ''LOGINNAME'': The account name* ''DOMAINNAME'': The domain name* ''SYSADMINRIGHTS'': Whether the user has administrator privileges in {{UBIK}} Studio* ''USE_DOMAIN_CREDENTIALS'': Whether to use Active Directory for authentication* ''PASSWORD'': The password* ''CONSUMER'': A link to the person this login is associated with (useful if there are multiple accounts per person) So, the steps to create a login are:# Find the system meta class ''LOGIN'' and drag it into a new bulk editor.# Create a new instance, filling in at least the ''LOGINNAME'', the ''DOMAINNAME'' and the ''PASSWORD''.# Save the new instance.

There is no fully prepared feature for user- or group-specific rights in {{UBIK}}. However, you can customize user rights and their consequencesexecution. 

First, it will be necessary to define what rights there should be. For exampleIn general, there could it should be possible to control whether a right user is allowed to see a specific type of object. Or maybeview ("read"), the right to see or edit specific properties of an object("write"), create and delete data. You Creation and deletion rights can create a meta class for user rights providing meta properties for all be subsumed into the details you might need, maybe even just a nameright to manipulate ("write") data.

The next step is So we have the basic definitions for reading and writing. Now we have to assign rights apply them to use-cases, respectively, objects and users. If you have user (or better, groups). E.g., the rights if it should be related possible to them. You can even define control the rights as specifically parameterized relation instances between a for editing an object's properties, one could relate the respective user group to the object and a set the right on the relation data object. Then, the group is related to the target object, with the respective right as a property of their relation connection.