A user represents a single person. Every action in Ooyala Flex is carried out by an authenticated Ooyala Flex user, and the actions available to a user (what they can see and do) are governed by their role and associated permissions.
Some other user rules are as follows:
• A user must belong to a single account.
• A user can own objects. In fact, all objects must have an owner (Ooyala Flex user).
• A user must have a single role.
• A user cannot do anything until they have authenticated themselves with Ooyala Flex, either through the Ooyala Flex console or through the API.
• Everything that a user does is logged through the creation of events.
The fields that belong to a user are as follows:
- Owner: Typically the person that created the user in the system.
• Login: The login is a unique string used by a user to identify themselves with the Ooyala Flex platform.
• Role: A user has a single role.
• Account: The account that the user belongs to.
• Groups: A collection of groups that the user belongs to.
• Workspaces: A collection of workspaces that the user belongs to.
The Master User
The master user is immutable and always exists. The master user is created when a new Ooyala Flex platform is installed, and is used for setting up other accounts and system-wide configuration. The master user owns the master account.
The System User
Users of Ooyala Flex will likely see events generated by a user called "system". The system user is immutable and always exists. This is the user that Ooyala Flex uses when it carries out work on behalf of a user.
User Object Properties
|Scope||Account, User||The scoping of this object|
|Visibility||Whether the object supports visibility|
|Extended Config.||Whether the object has an extended configuration tab|
|Scripting||Whether the object can be configured using scripting|
|Enable / Disable||Whether the object can be enabled and disabled|
|Start / Stop||Whether the object can be started and stopped|
|Copy||Whether the object can be copied|
|Export / Import||Whether the object can be exported and imported|
|Delete||Whether the object can be deleted|
|Unique Name||Whether the object name must be unique within its scope|
|Variants||Whether the object supports variants|