UnlockEditorSessionsForUser
Add a Building to a specific User, identified by username either as writeable or readonly. Method requires user to be of Type AuthorizationLevel::SUPERUSER
RPC Configuration
Rpc Name:
Plain: UnlockEditorSessionsForUser
Sha1: fafcf6b49d8901c8693bc78b9d5e13e9005b264f
RPCs can be called by their plain name or their SHA1 representation.
Rpc Parameters:
"building_id" : int,
"user_id" : int
Requires Login:
true
Requires Context:
The context providing parameter can either be a contagt-id (8-Bytes, Alphaumeric) or an integer as a building id. The context parameter name should make the choice obviouse, the type has not to be defined manually.
true
Requires contextParamName:
building_id
Requires WriteAccess:
Only accounts that have an explicit write access to the defined context can execute this RPC, no matter if the authentication level matches or not.
false
Requires AuthenticationLevel:
Authentication levels allow the SuperUser to define a by-RPC granular access configuration. If RPCs are chained in a single unified call and lenient is enabled, all allowed RPCs will be executed, while execution will fail entirely with lenient set to false.
SUPERUSER
Requires Subbuilding Merge Strategy:
REPLACE
Cache Configuration
All writing RPCs are not Cacheable, also Caching will be disabled by the paramters nocache
and readonly
.
Cache enabled:
true
Cache Time to Live:
60
Sample Request
->
{
"user_id": 4,
"building_id": 131
}
<-
true