Found 36 results for "access-control policies node-has-feature"

The search executed in 2.39034E-4 seconds. That's fast.

Policies

Policies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. The following types of policies are avail

Score: 36.689297

Access Policies

Access Policies This section describes features that are coming in 3.3. Access Control Policy documents are JSON documents that live at the Platform level. They provide a recipe that describes the access control that should be granted to any policy holder that is assigned the policy. Users may be assigned the policy directly, via a group or via a Team. Policy Document The Access Control Policy document provides a series of Statements that declare truths about what authority rights the policy hol

Score: 32.1208

Policies / Association Policies

Association Policies Association policies provide places where you can hook in behaviors that trigger when associations are created or removed between two nodes in the Cloud CMS content graph. When two nodes are connected together via an association or an association is broken, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAssociate Raised before an association is created between two nodes p:afterAssociate Ra

Score: 15.365261

Policies / Attachment Policies

Attachment Policies Attachment policies provide places where you can hook in behaviors that trigger when attachments are read, created, updated or deleted against a node. The following policies are available: Policy QName Description p:beforeReadAttachment Raised before a node's attachment is read p:afterReadAttachment Raised after a node's attachment is read p:beforeCreateUpdateAttachment Raised before an node's attachment is added to a node (either created or updated) p:afterCreateUpdateAttach

Score: 15.168722

Policies / Property Policies

Property Policies Property policies provide places where you can hook in behaviors that trigger when a property is created, updated or deleted. They allow you to get very granular about when you custom code is invoked - such as only when a specific property in your content is affected. The following property policies are available: Policy QName Description p:beforeCreateProperty Raised before a property on a node is created p:afterCreateProperty Raised after a property on a node is created p:bef

Score: 14.945507

Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 14.902065

Policies / Data List Policies

Data List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef

Score: 13.81526

UI Developers Guide / Contexts / access-policy-subcontext

access-policy-subcontext [ { "config": { "access-policy-subcontext": { "items": [ { "key": "access-policy", "title": "Access Policy", "order": 1000, "header": true, "items": [ { "key": "access-policy/properties", "title": "Properties", "uri": "{baseUri}/access-policies/{accessPolicyId}/properties", "order": 1000 },

Score: 6.0460525

Access Policies / Conditions

Conditions This section describes features that are coming in 3.3. Access Policy Conditions And Feature Matches ID Matches Locale Matches Node Type QName Matches Or Path Matches Project Matches Property Matches QName Matches Reference Matches Type Matches

Score: 6.0390906

Access Policies / Samples

Samples This section describes features that are coming in 3.3. Access Policy Samples Consumer of all Content Editor of all Content in Spanish Manager of all Content in a Folder

Score: 6.0390906

UI Developers Guide / Contexts / team-subcontext

team-subcontext [ { "config": { "team-subcontext": { "items": [ { "key": "team", "title": "Team", "order": 1000, "header": true, "items": [ { "key": "team/view", "title": "Overview", "uri": "#/teams/{teamId}", "order": 1000 }, { "key": "team/access-policies", "title": "Ac

Score: 5.866449

UI Developers Guide / Contexts / project-team-subcontext

project-team-subcontext [ { "config": { "project-team-subcontext": { "items": [ { "key": "team", "title": "Team", "order": 1000, "header": true, "items": [ { "key": "team/view", "title": "Overview", "uri": "#/projects/{projectId}/teams/{teamId}", "order": 1000 }, { "key": "team/access-po

Score: 5.809516

Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso

Score: 5.671233

UI Developers Guide / Contexts / project-user-context

project-user-context [ { "evaluator": "context-user", "config": { "project-user-context": { "items": [ { "key": "member", "title": "Project Member", "order": 1000, "header": true, "items": [ { "key": "member/overview", "title": "Overview", "uri": "#/projects/{projectId}/members/{principalId}", "iconClass": "fa fa-angle-right",

Score: 5.6451607

Security

Security Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe

Score: 5.635197

Content Modeling / Behaviors

Behaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b

Score: 5.6337767

UI Developers Guide / Actions / delete_access_policies

delete_access_policies ID: delete_access_policies This pops up a modal to ask the user if they'd like to delete the specified Access Policies. Upon confirmation, the Access Policies are deleted. Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1, policyId2]; UI.startAction(observableHolder, "delete_access_policies", actionContext, function(err) { // if something went wrong, err will contain the error // otherwise, success });

Score: 5.615373

UI Developers Guide / Contexts / platform-user-context

platform-user-context [ { "evaluator": "context-user", "config": { "platform-user-context": { "items": [ { "key": "user", "title": "User", "order": 1000, "header": true, "items": [ { "key": "user/overview", "title": "Overview", "uri": "{principalUri}", "iconClass": "fa fa-angle-right" }, {

Score: 5.609892

UI Developers Guide / Actions / unassign_access_policy

unassign_access_policy ID: unassign_access_policy This pops up a modal to ask the user if they'd like to unassign the specified Access Policies. Upon confirmation, the Access Policies are unassigned from the target (specified by ref). Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1]; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "unassign_access_policy", actionContext, function(er

Score: 5.5502925

Content Modeling / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: Association Policies function beforeAssociate(association)

Score: 4.777037

How does security work in Cloud CMS?

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 authorities

Score: 4.7746553

UI Developers Guide / Contexts / rule-subcontext

rule-subcontext [ { "config": { "rule-subcontext": { "items": [ { "key": "rule", "header": true, "title": "Rule", "items": [ { "key": "properties", "title": "Properties", "uri": "{projectUri}/rules/{documentId}", "order": 1000 }, { "key": "binding", "title": "Policies",

Score: 4.666104

Documentation - Getting Started - Cloud CMS

Documentation - Getting Started - Cloud CMS System Status Blog Support System Status Buy Now Features Quick Start Releases Pricing Documentation Developers Talk to Us Try Cloud CMS Features Quick Start Releases Pricing Docs Dev Start a Free Trial Features Quick Start Releases Pricing Documentation Developers Ask a Question Start a Free Trial Getting Started Content Modeling Role-Based Editorial UI Instant Preview Platform Multiple Projects Publishing Web Forms Workflow Workspaces Access Control

Score: 4.4778743

UI Developers Guide / Contexts / platform-manage-context

platform-manage-context [ { "evaluator": "context-platform", "config": { "platform-manage-context": { "items": [ { "key": "platform/manage/settings", "title": "Platform Settings", "uri": "#/settings", "cssClass": "dashboard-link", "order": 1000, "dashboardHeader": true, "iconClass": "fa fa-sliders", "allowAuthority": [ "owner", "manager",

Score: 4.3156924

How do I run custom validation before something is deleted?

Cloud CMS provides several ways to run validation ahead of deletion. There are many use cases where this employed - such as: Preventing an Image from being deleted when it is being referenced by a live Web Page Preventing a required sub-object from being deleted Preventing something from deleted when one or more other things are referencing it or depend on it in some way Here are a few approaches which are commonly used: ## Content Model Dependencies We implement link validation via the graph. S

Score: 4.3156924