Found 58 results for "manual topics permissions"

The search executed in 0.001 seconds

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: 22.096117

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: 17.234375

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: 7.794218

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: 6.588096

Application Server / Services / Broadcast

Broadcast The Broadcast service is responsible for relaying messages to members of the application server cluster. It provides an essential publish and subscription service so that application server members can broadcast messages, receive messages and subscribe to topics and events that occur throughout the system. Essential Configuration { "broadcast": { "enabled": , "type": "", "config": { ...configuration } } } There are two

Score: 6.0466537

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" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto

Score: 5.7556286

API / Data Types / Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This portion of the API therefore is largely for advanced users. The Cloud CMS API lets you dig in and poke around at the changeset history of branches to do things like

Score: 4.2561707

User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 3.9794421

User Interface / Security / 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: 3.8070278

Modules / Bindings

Bindings Actions Each action supports a binding like this: { "key": "{key}", (required) "title": "{title}", (required) "action": "{action}", "module": "{module}", "iconClass": "{iconClass}", "order": {order}, "allowPermission": [], "rejectPermission": [], "allowAuthority": [], "rejectAuthority": [] } The properties are defined as shown below: Property Type Required Description key string yes a unique key for the me

Score: 3.6319225

Platform

Platform Cloud CMS provides a Platform within which you can build out one or more Projects to create, manage and deliver your content. You can create as many Projects as you wish and are also free to duplicate, back up, download or export Projects at any time. Users You can add users to your Platform at any time. When users log in, they log in to the Platform and are then able to see all of the Projects that they have access to. You may choose to invite some users to have some permissions agains

Score: 3.5894022

API / Data Types / Identity

Identity Type identity Datastore Type directory Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Plan

Plan Type plan Datastore Type registrar Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Settings

Settings Type settings Datastore Type application Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Tenant

Tenant Type tenant Datastore Type registrar Supports authorities, permissions, transfer

Score: 3.4924953

API / Data Types / Archive

Archive Type archive Datastore Type registrar Supports authorities, permissions, transfer TODO

Score: 3.4847887

API / Data Types / Auto Client Mapping

Auto Client Mapping Type autoClientMapping Datastore Type webhost Supports authorities, permissions, transfer

Score: 3.4618719

User Interface / Security / 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, goto Manage Project and select Teams in the left nav 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 a look at the list

Score: 3.1694186

Modules / Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators

Score: 3.101534

User Interface / Workflow / View/Create a Workflow Model

View/Create a Workflow Model Switch to Platform level Click 'Workflow Models' (left Nav). Note: You will need to have admin or owner permissions to see the Workflow options. If you select a Workflow model you can Deploy, Undeploy, delete a Workflow model View/Edit Workflow Model Click on the Workflow name, eg Adhoc Approval, to view the Workflow Model To view/edit the Workflow click JSON Manage Active Workflow To see active instances of the workflow model click on Workflow option Note: you can s

Score: 2.984315

Create a Role

Cloud CMS lets you create custom roles for your organization. A role provides a mechanism for setting up security and access rights to your content. Roles also play an important part in customizing the user interface. Cloud CMS comes with several roles out of the box. You can also create your own at any time. To create and modify roles, you must be logged in as a manager or an administrator of your platform. Here are the steps to follow: Log into Cloud CMS and either create a project or navigate

Score: 2.85484

Traversal

Traversal Content in Cloud CMS is stored in a graph-like structure that consists of nodes and associations. Nodes are entities in the graph and associations are the relationships (the lines between points in the graph). As such, when working with content in Cloud CMS, you'll often find it useful to employ these structures in terms of your content model. Your content can be spread out between nodes and associations equally so that both the entities and the relationships hold JSON properties that

Score: 2.7546256

Role-based security access

You can configure a Cloud CMS project to provide precise, role-based access to content types and content instances. Let's take a look at example of how this is done! Suppose that you have three users - Jim, Dwight and Michael - and two content types (my:article and my:news). We would like things to work like this: Michael is the boss. He is allowed to view, create, edit and delete content content of all types. Dwight is a worker. He is allowed to view, create, edit and delete content of type "my

Score: 2.7546256

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: 2.7528749

Find

Find The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on

Score: 2.6558013