Users

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

Table 1.
Property Support Explanation
Scope Account, User The Scoping of this Object
Visibility Whether the Object supports visibility
Plugins Supports Plugins
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

Was this article helpful?