{"_id":"56cb83859f4ae20b00644f1f","user":"56c39c05bc41330d009f25d7","githubsync":"","category":{"_id":"56c7bab4606ee717003c4766","project":"56c35c56c0c4630d004e864c","__v":18,"pages":["56c7c193f9aa3b0d00c8458f","56cb80a4c675f50b00a4b826","56cb83859f4ae20b00644f1f","56cb853a245b841300806f82","56cb863c32011d2500681925","56cb88a4245b841300806f8b","56cb9915245b841300806fa7","56cb9a079f4ae20b00644f48","56cb9b5bc675f50b00a4b859","56cba5929f4ae20b00644f5d","56cba5c5d5c6241d00ef5e93","56cbab9c9f4ae20b00644f76","56cbad69c675f50b00a4b881","56cbb060d5c6241d00ef5ebb","56cf3c4d6c5d7a13005ee88c","56cf3d0e287eb20b009f9ec7","56cf3d7c5267d70b00494c42","56cf3ee0287eb20b009f9ecd"],"version":"56c35c56c0c4630d004e864f","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-02-20T01:00:36.607Z","from_sync":false,"order":0,"slug":"buzz-concepts","title":"Buzz Concepts"},"parentDoc":null,"project":"56c35c56c0c4630d004e864c","__v":4,"version":{"_id":"56c35c56c0c4630d004e864f","project":"56c35c56c0c4630d004e864c","__v":8,"createdAt":"2016-02-16T17:28:54.864Z","releaseDate":"2016-02-16T17:28:54.864Z","categories":["56c35c57c0c4630d004e8650","56c7b9e5379b311700ed8fe3","56c7bab4606ee717003c4766","56c7bb3613e5400d001e8cbd","56cf3f5a5267d70b00494c4b","56cf3f866c5d7a13005ee894","56fd3956caad892200847bce","599da256e7742b002588bb02"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"0.5.0","version":"0.5"},"updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-02-22T21:54:13.684Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":9,"body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Super User\"\n}\n[/block]\nA [User](doc:users) in Buzz can be set as a \"Super User\" by setting the `super_user` field to `true`. Only system administrators may be Super Users and only Super Users may create other Super Users.\n\nA Super User can do many things that normal Users cannot including:\n* Create and edit Accounts\n* Create and edit Global Creative Templates and Rules (i.e. those that go across accounts)\n* Create and edit Targeting Modules and Strategies\n* Create, view, edit, and delete objects in Accounts other than the one in which they belong\n* Create new Super Users.\n\nSuper Users are, however, still limited in their rights by the Roles and Permissions applied to them. For example, a Super User who does not have permission to create a new Creative Template, will not be able to create a Global Creative Template.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Multi-Account Users\"\n}\n[/block]\nA Buzz instance can be set up to support multiple [Accounts](doc:accounts). In order for a non-Super User to create and manage these Accounts, the `multi_account` settings must be set for that User.\n\nMulti-Account Users can:\n* Create and edit Accounts\n* Masquerade (authenticate) into other Accounts\n* Create, view, edit, and delete objects in Accounts other than the one in which they belong\n* Create new Multi-Account Users\n[block:api-header]\n{\n  \"title\": \"Whitelabeling Buzz\"\n}\n[/block]\nBuzz supports extensive whitelabeling capabilities, typically used in conjunction with Multi-Accounts (above).\n\nThe Buzz UI can be set behind a CNAME, such as `bidder.customername.com`.\n\nIn order to change the appearance of a Buzz instance, certain system variables need to be set manually in the underlying SQL database (not through the REST API). Please contact your Account Manager for more info.\n\nThe following system variables determine the behavior of the Buzz API and the appearance of the Buzz UI:\n[block:parameters]\n{\n  \"data\": {\n    \"h-0\": \"System Field\",\n    \"h-1\": \"Effect\",\n    \"0-0\": \"`WHITELABEL_COLOR_1`\",\n    \"0-1\": \"Main nav bar color\",\n    \"1-0\": \"`WHITELABEL_COLOR_2`\",\n    \"2-0\": \"`WHITELABEL_COLOR_3`\",\n    \"3-0\": \"`WHITELABEL_COLOR_4`\",\n    \"1-1\": \"Primary button, table header color\",\n    \"2-1\": \"Secondary button color\",\n    \"3-1\": \"Navbar text color\",\n    \"4-0\": \"`EMAIL_LOGO_URL`\",\n    \"4-1\": \"Location of logo to use in emails\",\n    \"5-0\": \"`EMAIL_PROJECT_NAME`\",\n    \"5-1\": \"Project name to use in emails and elsewhere. E.g. \\\"My Company's DSP\\\"\",\n    \"6-0\": \"`EMAIL_PROJECT_WEBSITE`\",\n    \"6-1\": \"URL to link to in emails\",\n    \"7-0\": \"`FROM_ADDRESS_NAME`\",\n    \"7-1\": \"From name for emails. Emails will still come from `no-reply:::at:::beeswax.com`\"\n  },\n  \"cols\": 2,\n  \"rows\": 8\n}\n[/block]\nThe parts of Buzz that cannot currently be whitelabeled are:\n\n1. Emails sent by the system come from `no-reply@beeswax.com`\n2. The Buzz REST API endpoint cannot use a CNAME\n3. Creative previews use a bidr.io URL","excerpt":"","slug":"super-users","type":"basic","title":"Super Users and Multi-Account Users"}

Super Users and Multi-Account Users


[block:api-header] { "type": "basic", "title": "Super User" } [/block] A [User](doc:users) in Buzz can be set as a "Super User" by setting the `super_user` field to `true`. Only system administrators may be Super Users and only Super Users may create other Super Users. A Super User can do many things that normal Users cannot including: * Create and edit Accounts * Create and edit Global Creative Templates and Rules (i.e. those that go across accounts) * Create and edit Targeting Modules and Strategies * Create, view, edit, and delete objects in Accounts other than the one in which they belong * Create new Super Users. Super Users are, however, still limited in their rights by the Roles and Permissions applied to them. For example, a Super User who does not have permission to create a new Creative Template, will not be able to create a Global Creative Template. [block:api-header] { "type": "basic", "title": "Multi-Account Users" } [/block] A Buzz instance can be set up to support multiple [Accounts](doc:accounts). In order for a non-Super User to create and manage these Accounts, the `multi_account` settings must be set for that User. Multi-Account Users can: * Create and edit Accounts * Masquerade (authenticate) into other Accounts * Create, view, edit, and delete objects in Accounts other than the one in which they belong * Create new Multi-Account Users [block:api-header] { "title": "Whitelabeling Buzz" } [/block] Buzz supports extensive whitelabeling capabilities, typically used in conjunction with Multi-Accounts (above). The Buzz UI can be set behind a CNAME, such as `bidder.customername.com`. In order to change the appearance of a Buzz instance, certain system variables need to be set manually in the underlying SQL database (not through the REST API). Please contact your Account Manager for more info. The following system variables determine the behavior of the Buzz API and the appearance of the Buzz UI: [block:parameters] { "data": { "h-0": "System Field", "h-1": "Effect", "0-0": "`WHITELABEL_COLOR_1`", "0-1": "Main nav bar color", "1-0": "`WHITELABEL_COLOR_2`", "2-0": "`WHITELABEL_COLOR_3`", "3-0": "`WHITELABEL_COLOR_4`", "1-1": "Primary button, table header color", "2-1": "Secondary button color", "3-1": "Navbar text color", "4-0": "`EMAIL_LOGO_URL`", "4-1": "Location of logo to use in emails", "5-0": "`EMAIL_PROJECT_NAME`", "5-1": "Project name to use in emails and elsewhere. E.g. \"My Company's DSP\"", "6-0": "`EMAIL_PROJECT_WEBSITE`", "6-1": "URL to link to in emails", "7-0": "`FROM_ADDRESS_NAME`", "7-1": "From name for emails. Emails will still come from `no-reply@beeswax.com`" }, "cols": 2, "rows": 8 } [/block] The parts of Buzz that cannot currently be whitelabeled are: 1. Emails sent by the system come from `no-reply@beeswax.com` 2. The Buzz REST API endpoint cannot use a CNAME 3. Creative previews use a bidr.io URL