This is the ThingsDB documentation for version v0, click here for the latest version!


Grant, collection or general, privileges to a user. Access to a user is provided by setting a bit mask to either the @node, @thingsdb or a @collection scope.

To use this function, at least EVENT privileges on the @thingsdb scope and GRANT privileges on the target scope are required.

It is not possible to set privileges on a specific node scope. Therefore scope @node will apply to all nodes in ThingsDB.

The following pre-defined masks are available:

Mask Description
QUERY (1) Gives read access.
EVENT (2) Gives modify access.
GRANT (4) Gives modify and grant (and revoke) privileges.
WATCH (8) Gives watch (and un-watch) privileges.
RUN (16) Gives run procedures access.
FULL (31) A mask for full privileges.

It is not possible to have GRANT privileges without also having EVENT privileges. However, ThingsDB automatically applies the required privileges so when setting for example GRANT privileges, ThingsDB makes sure that the user also gets EVENT privileges.

This function generates an event.


grant(target, user, mask)


Argument Type Description
target int/raw Can be either the @node, @thingsdb, or a @collection scope.
user str User to grant privileges to.
mask int Bit-mask for setting privileges.

Return value

Returns nil when successful. A lookup_err() is raised if the user or target does not exist.


Grant read and watch privileges to user iris to collection stuff:


// Assign WATCH privileges on all node scopes to user `iris`
grant('@node', 'iris', WATCH);

// Assign QUERY and WATCH privileges on collection `stuff` to user `iris`
grant('@:stuff', 'iris', QUERY|WATCH);

Return value in JSON format