Visibility levels - Public, Internal and Private

What does the visibility level affect?

The visibility level of an entity determines who can obtain information about it and/or interact with it.

Visibility level	State
Public	Grants access to everyone
Internal	Grants access to the entity only for authorized Users of the instance or for all Unit instances that belong to the instance
Private	Grants access to the entity only for its creator and agents specified by the creator. Works within the instance.

DANGER

The RepositoryRegisty entity is unique and has only two visibility types: Public and Private. Granting access to a Private entity works differently and is based on access credentials entered by Users.

The creator cannot grant access themselves; this is dictated by the business logic of this entity.

Capabilities of entity creators

The creator has full control over managing their entities.

RepositoryRegistry

• Change their own access credentials
• View repository size
• Create a Repo based on a RepositoryRegisty
• Update the Git repository inside Pepeunit
• Delete a RepositoryRegisty if it has no related Repo

Repo

• View distribution of Unit by versions
• Create Unit based on a Repo
• Update all related Unit
• Configure Repo
• Grant permissions
• Delete a Repo if it has no related Unit

Unit

• View information about the current version of a Unit
• View information about the state of a Unit
• Set env.json
• Download Firmware and compiled packages
• Send update commands over MQTT: Firmware, Schema and Env
• Configure a Unit
• Grant permissions
• Delete a Unit

UnitNode

• View state
• Set values with sending to Input via MQTT
• Create connections for Input
• Configure UnitNode
• Grant permissions
• Manage all aspects of DataPipe

Capabilities of agents for visible entities

Agents have limited access to foreign entities that they can see using the visibility system:

RepositoryRegistry

• Change their own access credentials
• View repository size. Available for both Private and Public repositories regardless of access credentials
• Create a Repo based on a RepositoryRegisty. For Public — available to everyone; for Private — only if the access credentials have status Valid
• Update the Git repository inside Pepeunit. For Public — available to everyone; for Private — only if the access credentials have status Valid

Repo

• View distribution of Unit by versions
• Create Unit based on a Repo

Unit

• View information about the current version of a Unit
• View information about the state of a Unit

UnitNode

• View state
• Set values with sending to Input via MQTT
• Create connections for Input