Found 397 results for "access-policies conditions project"
The search executed in 0.001664062 seconds. That's fast.
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Data StoreData Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val
Score: 1.9332339
|
|
Gitana / 3.2 / Guide / Guide / UI Developers GuideUI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial
Score: 1.8804046
|
|
Gitana / 4.0 / Developers / User Interface Customization / OverviewUI Developers Guide The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature-complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired editorial
Score: 1.8804046
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / ConfigurationConfiguration The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]
Score: 1.8478385
|
|
Gitana / 4.0 / Developers / User Interface Customization / ConfigurationConfiguration The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]
Score: 1.8478385
|
|
Gitana / 3.2 / Guide / Guide / Deployment / Deployment StrategyDeployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ
Score: 1.6457982
|
|
Gitana / 4.0 / Data Engine / Deployment / Deployment StrategyDeployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ
Score: 1.6457982
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / registrationsregistrations [ { "config": { "registrations": { "menus": [ { "scope": "platform", "key": "account-context", "text": "Account" }, { "scope": "platform", "key": "archive-subcontext", "text": "Archive" }, { "scope": "platform", "key": "vault-subcontext", "text": "Vault" }, { "scope": "platfo
Score: 1.5488818
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / registrationsregistrations [ { "config": { "registrations": { "menus": [ { "scope": "platform", "key": "account-context", "text": "Account" }, { "scope": "platform", "key": "archive-subcontext", "text": "Archive" }, { "scope": "platform", "key": "vault-subcontext", "text": "Vault" }, { "scope": "platfo
Score: 1.5488818
|
|
Gitana / 3.2 / Guide / Guide / Publishing / Example Publishing SetupExample Publishing Setup The following are the steps to config a typical Publishing setup (Publish and Unpublish): Step 1: Create Projects Create two projects Create an "Authoring" project Create a "Live" Project Step 2 : Create a Deployment Target Deployment Target is the endpoint where the package will be deployed or sent. Go to Manage Platform Go to Deployment Targets under Deployment Left Navigation Menu Click on Create a Deployment Target Title : "Live Web Site" Deployment Target Type : "Br
Score: 1.520459
|
|
Gitana / 4.0 / Data Engine / Publishing / Example Publishing SetupExample Publishing Setup The following are the steps to config a typical Publishing setup (Publish and Unpublish): Step 1: Create Projects Create two projects Create an "Authoring" project Create a "Live" Project Step 2 : Create a Deployment Target Deployment Target is the endpoint where the package will be deployed or sent. Go to Platform Go to Deployments Targets under Deployments Left Navigation Menu Click on Create a Deployment Target Title : "Live Web Site" Deployment Target Type : "Branch"
Score: 1.5112357
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Samples / Releases Menu ItemReleases Menu Item In Cloud CMS, Releases describes the ability for the product to allow multiple branches to be forked, merged and scheduled for automatically promotion of content to a live environment. It offers scheduled publishing, conflict detection and offers an ideal solution for editors to coordinate the delivery of content in situations where multiple editorial efforts may be running concurrently. When Releases is enabled for a Project, a Releases menu item shows up in the left-hand men
Score: 1.5006042
|
|
Gitana / 4.0 / Developers / User Interface Customization / Samples / Releases Menu ItemReleases Menu Item In Cloud CMS, Releases describes the ability for the product to allow multiple branches to be forked, merged and scheduled for automatically promotion of content to a live environment. It offers scheduled publishing, conflict detection and offers an ideal solution for editors to coordinate the delivery of content in situations where multiple editorial efforts may be running concurrently. When Releases is enabled for a Project, a Releases menu item shows up in the left-hand men
Score: 1.5006042
|
|
Gitana / 3.2 / Guide / Guide / User Interface / ProjectsProjects Deleted Items Configure Locales Copy a Project Create a Project Delete a Project Export a Project Import a Project Configure Search
Score: 1.4855449
|
|
Gitana / 4.0 / User Interface / Projects / OverviewProjects Deleted Items Configure Locales Copy a Project Create a Project Delete a Project Export a Project Import a Project Configure Search
Score: 1.4855449
|
|
Limiting Folder Access to Specific UsersWhen you create a Project in Cloud CMS, the Project is automatically configured with a Project Users team that grants the Consumer role to any project members. As a result, any members of the Project will have the ability to see all content within the Project. For many, this works just fine. However, there may be cases where you want to limit certain Folders to only be accessible by specific Users. Let's walk through some steps on how to do this. Change the Project Users team security policy Fir
Score: 1.4791905
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / publishing-manage-subcontextpublishing-manage-subcontext [ { "evaluator": "context-project", "config": { "publishing-manage-subcontext": { "items": [ { "key": "project/publishing", "title": "Publishing", "header": true, "items": [ { "key": "project/publishing/settings", "title": "Settings", "uri": "#/projects/{projectId}/manage/publishing", "iconClass": "fa fa-angle
Score: 1.4769733
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / publishing-manage-subcontextpublishing-manage-subcontext [ { "evaluator": "context-project", "config": { "publishing-manage-subcontext": { "items": [ { "key": "project/publishing", "title": "Publishing", "header": true, "items": [ { "key": "project/publishing/settings", "title": "Settings", "uri": "#/projects/{projectId}/manage/publishing", "iconClass": "fa fa-angle
Score: 1.4769733
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / Multiple ProjectsMultiple Projects A Project is a collaboration space where a team of users can work together on the creation, approval and publication of content. You invite people to projects using their email addresses. You can create as many Projects as you'd like. Once you've invited people to a project, they will be able to sign on to your Platform and work within that individual project. You can invite them to other projects as well. Within each project, they will have rights and access to things based on
Score: 1.4747154
|
|
Gitana / 4.0 / Getting Started / Using your Data Platform / ProjectsProjects A Project is a collaboration space where a team of users can work together on the creation, approval and publication of content. You invite people to projects using their email addresses. You can create as many Projects as you'd like. Once you've invited people to a project, they will be able to sign on to your Platform and work within that individual project. You can invite them to other projects as well. Within each project, they will have rights and access to things based on the Role
Score: 1.4747154
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Samples / Developer Menu ItemsDeveloper Menu Items By default, the Developer menu group is not enabled for users with the 'collaborator' role. Here is an example of how to change the default behavior of Cloud CMS to allow Developer menu options for users with the 'collaborator' role. We could use the following configuration: { "config": { "blocks": [ { "evaluator": "context-project", "config": { "project-context": { "items": [
Score: 1.4728019
|
|
Gitana / 4.0 / Developers / User Interface Customization / Samples / Developer Menu ItemsDeveloper Menu Items By default, the Developer menu group is not enabled for users with the 'collaborator' role. Here is an example of how to change the default behavior of Cloud CMS to allow Developer menu options for users with the 'collaborator' role. We could use the following configuration: { "config": { "blocks": [ { "evaluator": "context-project", "config": { "project-context": { "items": [
Score: 1.4728019
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / releases-contextreleases-context [ { "evaluator": "context-project", "config": { "releases-context": { "items": [ { "key": "project/releases", "title": "Releases", "header": true, "order": 10000, "items": [ { "key": "project/releases/calendar", "title": "Calendar", "uri": "#/projects/{projectId}/releases/calendar", "iconClass": "fa fa-angle-r
Score: 1.4603724
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / releases-contextreleases-context [ { "evaluator": "context-project", "config": { "releases-context": { "items": [ { "key": "project/releases", "title": "Releases", "header": true, "order": 10000, "items": [ { "key": "project/releases/calendar", "title": "Calendar", "uri": "#/projects/{projectId}/releases/calendar", "iconClass": "fa fa-angle-r
Score: 1.4603724
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / uitemplates-subcontextuitemplates-subcontext [ { "config": { "uitemplates-subcontext": { "items": [ { "key": "project-uitemplates", "title": "Project UI Templates", "header": true, "order": 1000, "items": [ { "key": "project/uitemplates/settings", "title": "Settings", "uri": "#/projects/{projectId}/uitemplates/settings", "iconClass": "fa fa-sliders"
Score: 1.4434587
|