Wallboard is an all-in-One Digital Signage Solution.
Our users can create their own digital signage content using our web-based editor.
Our cloud integration feature lets our users connect their Google drive account to our system so they can display images and videos in their signage contents.
We use the calendar integration for our meeting room solution where our users can create meeting room scheduler and manager signage contents.
I will need “/auth/calendar.readonly” in order to read information about the user’s calendar so that my app can provide a data feed to the user including details of their connected calendar.
I will need “/auth/calendar.events” in order to read, create, modify and delete events from the user’s calendar so that my app can provide an interface as part of a meeting room manager signage content.
A narrower scope would not be sufficient because our application needs write access as well as read so that our users can schedule, delete and modify meetings at their meeting rooms.
These meetingrooms and the meetings taking place in there represent the user’s calendar and the events in it.
I will need “/auth/drive.metadata.readonly” in order to retrieve information about the user’s Google drive file system so that my app can display the folder structure for the user.
The users will select the folders and files they want to synchronize to our application from this list.
I will need “/auth/drive.readonly” in order to read the user’s Google drive file system so that my app can synchronize them to our local storage and the user can embed these files in their digital signage contents.
Our synchronization is strictly one way, we do not create, edit or delete the user’s files on their Google drive.
When files are deleted from the user’s Google drive, our application will also delete our copy of it.
We only synchronize files and folders selected by the users themselves.
I will need “/auth/spreadsheets” in order to create spreadsheets so that my app can help our users by creating a new template spreadsheet and navigating their browser to it.
A narrower scope would not be sufficient because our application needs write access to create these template spreadsheets.