Optional
data: PartialMessage<proto.badges.CollectionPermissions>Permissions related to archiving the collection.
Permissions related to deleting the collection.
Permissions related to updating badge metadata for specific badges.
Permissions related to updating collection approvals.
Permissions related to updating the metadata of the collection.
Permissions related to updating custom data for the collection.
Permissions related to updating the collection's manager.
Permissions related to updating off-chain balances metadata.
Permissions related to updating standards for the collection.
Permissions related to creating more badges for the collection.
Static
Readonly
fieldsStatic
Readonly
runtimeStatic
Readonly
typeStatic
equalsStatic
fromOptional
options: Partial<BinaryReadOptions>Static
fromOptional
options: Partial<JsonReadOptions>Static
fromOptional
options: Partial<JsonReadOptions>
CollectionPermissions defines the permissions for the collection (i.e., what the manager can and cannot do).
There are five types of permissions for a collection: ActionPermission, TimedUpdatePermission, TimedUpdateWithBadgeIdsPermission, BadgeIdsActionPermission, and CollectionApprovalPermission.
The permission type allows fine-grained access control for each action.
Note there are a few different times here which could get confusing:
The permitted/permanentlyForbiddenTimes are used to determine when a permission can be executed. Once a time is set to be permitted or forbidden, it is PERMANENT and cannot be changed. If a time is not set to be permitted or forbidden, it is considered NEUTRAL and can be updated but is ALLOWED by default.
IMPORTANT: We take first-match only for the permissions. This means that if you forbid time T in array index 0 and permit time T in index 1, we will only check the first permission (forbid time T) and not the second permission (permit time T).
Generated
from message badges.CollectionPermissions