{"__v":12,"_id":"567b414217368a0d009a6e5c","category":{"__v":12,"_id":"55562a5526e9bc0d0044ea47","pages":["5556300926e9bc0d0044ea6e","567b40b17c40060d0056042b","567b40c23241c20d00b7308c","567b40e23241c20d00b7308e","567b40f693919f0d00c97ad7","567b413593919f0d00c97ada","567b414217368a0d009a6e5c","567b4152ee052b1700dbd9e7","567b416093919f0d00c97adc","567b418417368a0d009a6e5e","567b41b917368a0d009a6e60","567f2a9fa74a1c0d003e1fce"],"project":"555627c4ea5e120d001884fb","version":"555627c4ea5e120d001884fe","reference":false,"createdAt":"2015-05-15T17:18:13.646Z","from_sync":false,"order":4,"slug":"manage-teams-items","title":"Flite Console"},"project":"555627c4ea5e120d001884fb","user":"55562799ea5e120d001884f8","version":{"__v":10,"_id":"555627c4ea5e120d001884fe","project":"555627c4ea5e120d001884fb","hasDoc":true,"hasReference":true,"createdAt":"2015-05-15T17:07:16.918Z","releaseDate":"2015-05-15T17:07:16.918Z","categories":["555627c5ea5e120d001884ff","55562a5526e9bc0d0044ea47","555653821026001900d72a3c","5556685c1026001900d72a85","5556687626e9bc0d0044ec04","555668821026001900d72a87","55566892150ba30d00f4e206","555668b826e9bc0d0044ec05","55e0fb6026f51b0d009b1746","567b3b3017368a0d009a6e54"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"1.0.0","version":"1.0"},"updates":[],"createdAt":"2015-12-24T00:50:10.814Z","link_external":false,"link_url":"","githubsync":"","sync_unique":"","hidden":false,"api":{"results":{"codes":[]},"settings":"","auth":"required","params":[],"url":""},"isReference":false,"order":7,"body":"The Flite Console allows you to organize all your items—including ads, components, mobile apps, etc.—into folders. It also allows your organization's administrator to permission those folders in a way that gives all the right people access to each folder.\n\nThe typical workflow is for the administrator to build out a folder structure that makes sense for your organization and that makes it clear who has access to each folder. Then non-admin users can place the items they create in the appropriate folders.\n\nAn item can live in multiple folders at once. For instance, suppose your organization's folder structure directly corresponds to its team structure, with each team having its own folder. To share an item with multiple teams, you will want to place it in each team's folder.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Managing Folders\"\n}\n[/block]\nFolders allow you to organize your creative assets in the Console. To create a new folder, do the following:\n1. Click on *Make New Item* on the left hand side.\n  * To create a new top-level folder, mouse over the *Items* heading.\n  * To create a sub-folder of an existing folder, mouse over the existing folder.\n2. A new folder entry appears at the bottom of the existing folder list.\n3. Type in the folder name and hit *Enter*.\n\nYou have just created a new folder. To populate the folder, simply find the item you want and drag-and-drop it into the new folder. You can drag-and-drop from the *All Items* or *My Items* list, or from another folder. Only the items for which you have Edit permissions will be draggable. Note that dragging and dropping an item from an existing folder will not remove it from that folder.\n\nTo delete your folder, do the following:\n1. Mouse over the folder name in the sidebar until the :fa-cog: shows up.\n2. Click the gear menu, and select *Delete Folder*.\n3. Click the *Delete Folder* button in the confirmation dialog.\n\nYou have just deleted a folder. \n[block:callout]\n{\n  \"type\": \"info\",\n  \"body\": \"Deleting a folder does not delete its contents. It just removes the items from that folder.\",\n  \"title\": \"NOTE\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Applying Permissions to Folders\"\n}\n[/block]\nPermission management is an admin only task. You must have admin-level access to the Flite Console to be able to manage permissions for the teams and folders in your organization.\n\nTo change permissions for Team X on Folder A, do the following:\n1. Click the folder name in the sidebar.\n2. Click the *Permissions* button that appears in the header.\n3. Click the team name in the permissions screen that appears.\n4. Drag the bar to the appropriate permission level (None, View, Edit, or Full). See Permissions view below for more on what each permission level means.\n\nYou have just changed the permissions for a team. Team X will now have the access level you set for Folder A\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Permissions View (Admin Only)\"\n}\n[/block]\nYou can access the Permissions screen for any folder by clicking on that folder and then clicking the Permissions button at the top of the folder's items listing. The Permissions screen contains a list of all teams in your organization, as well as any external teams with access to your organization.\n\nNote: You can access the Permissions screen for a set of resources (e.g. ad components or ad templates) as described in the Resource Selection page documentation. Because setting permissions for folders is much more common, we will use folders as the example for the remainder of this article. However, setting permissions for resources is the same as for folders.\n\nNext to each team's name is a slider. Drag the slider to the appropriate spot to set the permission level that team will have to this folder. The available permission levels, in order from most restrictive to least restrictive, are:\n\n  * **None:** This means team members will not be able to view this folder and its contents. It simply will not show up in their Console.\n  * **View:** This means the team members will be able to view the contents of this folder, but will not be able to edit them. They will not be able to place items into the folder or remove items from the folder. And they will only be able to see preview versions of the various items (ads, components, etc.) in the folder.\n  * **Edit:** This means the team members will be able to edit the contents of this folder. They will be able to add items to the folder, remove items from the folder, and edit the various items (ads, components, etc.) contained in the folder.\n  * **Full:** This means the team members will be able to manipulate everything about this folder. In addition to viewing and editing everything about the folder and its contents, they will also be able to add subfolders, rename the folder, and delete the folder from the Console. \n\nWhen setting permissions for teams, remember that a child team cannot have a lower permission level on a folder than its parent.\n\nAt the bottom of the Permissions screen are two buttons:\n  * **Apply Changes:** Click this button once you are done making changes to the folder's permissions. Your changes will not be saved until you click this button, so don't forget to do it!\n  * **Cancel:** Click this button to cancel your changes and revert to the last saved version of the permissions for this folder.","excerpt":"","slug":"console-folders-and-permissions","type":"basic","title":"Folders & Permissions"}

Folders & Permissions


The Flite Console allows you to organize all your items—including ads, components, mobile apps, etc.—into folders. It also allows your organization's administrator to permission those folders in a way that gives all the right people access to each folder. The typical workflow is for the administrator to build out a folder structure that makes sense for your organization and that makes it clear who has access to each folder. Then non-admin users can place the items they create in the appropriate folders. An item can live in multiple folders at once. For instance, suppose your organization's folder structure directly corresponds to its team structure, with each team having its own folder. To share an item with multiple teams, you will want to place it in each team's folder. [block:api-header] { "type": "basic", "title": "Managing Folders" } [/block] Folders allow you to organize your creative assets in the Console. To create a new folder, do the following: 1. Click on *Make New Item* on the left hand side. * To create a new top-level folder, mouse over the *Items* heading. * To create a sub-folder of an existing folder, mouse over the existing folder. 2. A new folder entry appears at the bottom of the existing folder list. 3. Type in the folder name and hit *Enter*. You have just created a new folder. To populate the folder, simply find the item you want and drag-and-drop it into the new folder. You can drag-and-drop from the *All Items* or *My Items* list, or from another folder. Only the items for which you have Edit permissions will be draggable. Note that dragging and dropping an item from an existing folder will not remove it from that folder. To delete your folder, do the following: 1. Mouse over the folder name in the sidebar until the :fa-cog: shows up. 2. Click the gear menu, and select *Delete Folder*. 3. Click the *Delete Folder* button in the confirmation dialog. You have just deleted a folder. [block:callout] { "type": "info", "body": "Deleting a folder does not delete its contents. It just removes the items from that folder.", "title": "NOTE" } [/block] [block:api-header] { "type": "basic", "title": "Applying Permissions to Folders" } [/block] Permission management is an admin only task. You must have admin-level access to the Flite Console to be able to manage permissions for the teams and folders in your organization. To change permissions for Team X on Folder A, do the following: 1. Click the folder name in the sidebar. 2. Click the *Permissions* button that appears in the header. 3. Click the team name in the permissions screen that appears. 4. Drag the bar to the appropriate permission level (None, View, Edit, or Full). See Permissions view below for more on what each permission level means. You have just changed the permissions for a team. Team X will now have the access level you set for Folder A [block:api-header] { "type": "basic", "title": "Permissions View (Admin Only)" } [/block] You can access the Permissions screen for any folder by clicking on that folder and then clicking the Permissions button at the top of the folder's items listing. The Permissions screen contains a list of all teams in your organization, as well as any external teams with access to your organization. Note: You can access the Permissions screen for a set of resources (e.g. ad components or ad templates) as described in the Resource Selection page documentation. Because setting permissions for folders is much more common, we will use folders as the example for the remainder of this article. However, setting permissions for resources is the same as for folders. Next to each team's name is a slider. Drag the slider to the appropriate spot to set the permission level that team will have to this folder. The available permission levels, in order from most restrictive to least restrictive, are: * **None:** This means team members will not be able to view this folder and its contents. It simply will not show up in their Console. * **View:** This means the team members will be able to view the contents of this folder, but will not be able to edit them. They will not be able to place items into the folder or remove items from the folder. And they will only be able to see preview versions of the various items (ads, components, etc.) in the folder. * **Edit:** This means the team members will be able to edit the contents of this folder. They will be able to add items to the folder, remove items from the folder, and edit the various items (ads, components, etc.) contained in the folder. * **Full:** This means the team members will be able to manipulate everything about this folder. In addition to viewing and editing everything about the folder and its contents, they will also be able to add subfolders, rename the folder, and delete the folder from the Console. When setting permissions for teams, remember that a child team cannot have a lower permission level on a folder than its parent. At the bottom of the Permissions screen are two buttons: * **Apply Changes:** Click this button once you are done making changes to the folder's permissions. Your changes will not be saved until you click this button, so don't forget to do it! * **Cancel:** Click this button to cancel your changes and revert to the last saved version of the permissions for this folder.