Search Results

API / Security / Security

Security Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based au

Score: 59.902813

API / Security / Permissions

Permissions Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit

Score: 10.4183445

UI Guide / User Management / Create a new Role

Create a new Role The Roles for a Project can be managed on the Roles page. For reference, here are the default Roles available: Let's take a look at the list of the default roles: Roles Description Collaborator “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “DELETE” Connector “CONNECT” Consumer "CONNECT”, “READ” Contributor “CONNECT”, “READ”, “CREATE_SUBOBJECTS” Editor “CONNECT”, “READ”, “UPDATE”, “DELETE” Impersonator “IMPERSONATE” Manager “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “

Score: 9.666946

UI Guide / User Management / Create a new Team

Create a new Team The Teams for a Project can be managed on the Teams page: First Step is to create the Team In your project, select Teams in the left nav (near the botton of the Left Nav options) To Create a new Team click 'Create Team' Second Step is to add Roles to the team Under Teams, click on your newly created team Select Roles Click '+Grant Role' Select the Roles you want for the Team. Note: if you do not see the Role(s) needed for your Team you will need to create the Roles. Let's take

Score: 9.006265

API / Security / Authorities

Authorities Every data store and object in Cloud CMS maintains access control lists so that you can finely describe the rights of any principal in the system against it. This lets you finely tune the rights of individual users against data stores and objects down to a single permission. This access control is authority-based which means that it's applied by granting authorities (or roles) that a principal has over an object. Let's buckle down on the terminology for a moment: A Permissioned entit

Score: 7.5538435

UI Developer Guide / Evaluators / User

User current-user-has-authority If the currently logged in user has the given authority over the current entity being observed. { "evaluator": "current-user-has-authority", "condition": "{authorityId}" } current-user-has-permission If the currently logged in user has the given permission over the current entity being observed. { "evaluator": "current-user-has-permission", "condition": "{permissionId}" }

Score: 6.0316916

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 5.797893

API / Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 5.657179

Fine Tuning User Management

Teams provide a very broad way to assign authorities. If a Team grants the Consumer authority, say, it grants that authority over everything in the project. That means all content is readable by anyone on the team. While this is useful in a number of cases, it is also too broad a stroke for more complex scenarios. In a more complex scenario where you wish to limit read access for specific types of content to specific users. To do this, you start by modifying your Teams so they no longer do that

Score: 5.3865185

API / Content Services / Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" quyery operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS aut

Score: 5.284949