Roles decide what people can do
Five roles, from View only to Administrator. A Content Editor builds content. Only a Content Manager or above puts it on screens.
Govern complexity and simplify work
The person who designs your menu boards and the person who changes tonight’s price need different things from Wallboard. A small central team builds the structure. That means folders and templates, brand kits, and the rules about who publishes. A much larger group, spread across stores, campuses or departments, needs to change a price or a notice and get back to work. We give the central team control over what everyone else can see and do, and everyone else a short path to the one change they came to make.
Five roles, from View only to Administrator. A Content Editor builds content. Only a Content Manager or above puts it on screens.
Give each region or department its own devices, content items and files. Share each one read-only or with read and write access.
User interface profiles hide the menus and buttons someone doesn’t use, and no profile can grant more than the person’s role allows.
Logos, five color slots and three font slots. Bind them to a template once. Switch kits later and the same design re-skins itself.
The designer marks which fields may change, and everyone else edits only those fields, with a preview of the finished screen beside them.
The five roles and what each can do. How a manager signs off an editor’s work before it reaches a screen.
Content and slide designers, template folders and brand kits. For the people who set the design standard.
Quick Edit, focused interface profiles and a spreadsheet link that needs no login. Built for staff who update screens now and then.
Single sign-on, SCIM, enforced two-factor sign-in and activity logs.
Your directory already knows who works where. With SAML single sign-on, your identity provider can pass a person’s role, team membership and interface profile to Wallboard each time they sign in. Plan that mapping before you switch it on, because if a sign-in arrives without the expected attribute, the user loses that role, team or profile at the next login. SCIM 2.0 from Entra ID, Okta or OneLogin runs the rest of the account lifecycle. It creates and updates users, and deactivates leavers, without an administrator touching them.
Review security controlsA permission table tells you the rules, but not what a given person sees. Administrators can open View as and look at Wallboard the way a team or a named user sees it, with a colored banner that says which view is active. If you change a personal setting such as a table layout while viewing as somebody, Wallboard asks whether to save it to their account or keep it local. Afterwards, the Logs page filters activity by user, device, content or datasource. Use the Audit filter and export to CSV.
Editors’ changes reach screens only through a manager. Approval comes from the roles, not from a separate queue. A Content Editor can’t save changes to content that is already assigned to a screen, so they duplicate it and edit the copy, and a Content Manager reviews that copy and assigns it. Teams decide who works on which content. A regional marketing lead only reviews her own region’s work.
See how roles workMost of the planning in a rollout goes into mapping your org chart onto roles and teams, then onto interface profiles. If you want a second opinion, write to support@wallboard.us. The team answers on weekdays 08:00 - 17:00 CST.
Tell us who designs, who approves and who updates screens today. We’ll map it onto roles and teams in the demo.