Datasheet

Acano X Series Server and Virtualized Deployments
Acano Solution R1.6: Support FAQs 76-1022-08-K
Page 25
a. Use the GET method to https://<server IP address>/api/v1/coSpaces.
4. Associate the CallLegProfile with the coSpace.
a. Use the PUT method to https://<server IP address>/api/v1/cospaces/<coSpace_ID>,
with the body as callLegProfile=<callLegProfile_ID>
Encryption is now enforced on all calls in this coSpace. (You can also enforce encryption at
tenant level or associate it with access methods.)
I see that different members of the same coSpace can have different
permissions on that coSpace. How does this occur?
From R1.2 members of a coSpace can have the following permissions set either automatically or
manually. The default permissions for users depend on the way in which they become a
member.
 When adding or modifying a coSpace member via the API you can set/update the following
(see the API Reference for details) without any cross-dependencies or limitations:
 canDestroy
 canAddRemoveMember
 canChangeName
 canChangeUri
 canChangeCallId
 canChangePasscode
 canPostMessage
 canRemoveSelf
 From an Acano client (depending on client type and version) members with
canAddRemoveMember set to true can add other users as members of the coSpace. New
members have identical permissions to the member who added them, except in one case:
when the original member also has canRemoveSelf set to false.
Members who cannot remove themselves from the coSpace (as controlled by
canRemoveSelf) should not be able to create a second member in order to delete their own
membership. Therefore any member created from an Acano client by another member in
this situation will have canAddRemoveMember set to false and canRemoveSelf set to true.
All other permissions are copied from the original member.
 Auto-generated members (created by an LDAP sync) have auto-generated permissions
because it makes no sense to allow them to make changes that will be overwritten by the
next LDAP sync. Therefore, for these users the following parameters are always set to false:
canDestroy, canChangeName, canChangeUri, canChangeCallId and canRemoveSelf. The
other “can” parameters above are set to true. Note that changing any of these settings for an
auto-generated member via the API will only have a temporary effect and will be overwritten
at the next LDAP sync.
 If a user creates a coSpace from the Acano client, then all members get all permissions (all
“can” parameters above are set to true by default.