Supper

Script to generate a seating plan via calendar events in an organisation’s Office365.

What it does

Supper looks at the current week and generates a seating plan for that week. By getting the calendar of a dedicated room or account, it can see who will be out of the office during the week. It then creates a CSV of who will be in the office on the 5 days of the week.

Note: Current week is defined during the normal workweeks. If the script is run on the weekend (Saturday and Sunday) the script will generate next weeks and label it as such.

Requirements

Supper requires:

• Python 3.5 <=
• Admin access to an Org’s Office365

Warning: This guide assumes you are using a UNIX based OS (Linux, Mac OS, etc.). If using Windows, god help you.

Pre-Install

To setup the script, you will need to create an app in your organisation Azure Active Directory. You can find the app registration page here.

For a guide on how to do this, see the guide provided by python-o365 below.

To work with OAuth you first need to register your application at Azure App Registrations.

1. Login at Azure Portal (App Registrations)
2. Create an app. Set a name.
3. In Supported account types choose “Accounts in any organizational directory.
4. Set the redirect uri (Web) to: https://login.microsoftonline.com/common/oauth2/nativeclient and click register. This is the default redirect uri used by this library, but you can use any other if you want.
5. Write down the Application (client) ID AND Directory (tenant) ID. You will need these values.
6. Under “Certificates & secrets”, generate a new client secret. Set the expiration to never.
7. Write down the value of the client secret created now. It will be hidden later on.
8. Under API Permissions add the delegated permissions for Microsoft Graph you want

The required API Permissions are:

Calendars.Read.Shared
User.Read
User.ReadBasic.All
offline_access

Installation

Once the app has been created, git clone this repo, cd into its folder and install it into your user’s Python PATH.

git clone URL
cd supper
python3 -m pip install . --user

This installs the script to your Python user bin.

Configuration

ID’s and Secrets

Now we need to create a config file. This will store all the values we wrote down when creating our application (id, secret, tenant). It will also include some other information that is required to run Supper. This needs to be created by you. Let’s create one in the user config folder. This is where Supper will look for a config file by default.

touch ~/.config/supper.yaml

This should create an empty YAML file. Open up this file with your text editor of choice and copy and paste this example.

client_id: "CLIENT_ID"
client_secret: "CLIENT_SECRET"
tenant_id: "TENANT_ID"
ooo_email: "example@example.com"
users: ["Bob", "Alice"]

Replace CLIENT_ID, CLIENT_SECRET, and TENANT_ID with the values from the Azure website we wrote down earlier. Replace ooo_email with the email of the calendar that has the out of office events. Replace users with a list of all the first names of employee’s in your organisation. This is case insensitive but has to be spelt the same as their Office365 accounts.

Note: If you are trying to find this file in a file browser and cannot find it, ~/.config is a hidden directory and you will need to enable viewing hidden directories and files in your file browser.

Running the program

Now we have configured everything, we can now run the script. To run the script, enter this inside of the terminal.

supper

This will generate a Seating Plan.csv file in the directory you ran this program. Look at Output to see how to configure the file name of the output.

The first time the script is ran, it will ask you to visit a url. Open the url in your browser and allow the script access to the requested permissions. Once you have done that, you will be redirected to a blank page. Copy the URL and paste it into the console and press enter.

Note: You should login as a user with full permissions to the out of office calendar. This is to ensure the script has permissions to view this calendar in full. This will only need to be done every 90 days.

Command Arguments

Config

If you want to store the config file in a different directory than the default (/home/$USER/.config/supper.yaml), you can provide the location of the config file using the --config or -c flag.

supper -c ~/.supper.yaml

Output (Recommended)

You can configure the output path too. Normally, the script will output a file called Seating Plan.csv in the directory you ran the script in. This can be edited with the --output or -o flag. We can put the file in a different folder and have a different name like this:

supper -c ~/.config/supper.yaml -o "/path/to/file"

For example, we can generate a CSV in our user’s Documents folder and name it “Who’s in office?”

supper -c ~/.config/supper.yaml -o "~/Documents/Who's in office" # If you don't provide a .csv file extension, it will be added for you.

This also supports datetime formatting. This can be done using Python’s formatting codes for datetime which you can find the docs for here. When the script is executed, the datetime provided in the string will be set using the start of the weeks date (Monday).

supper -c ~/.config/supper.yaml -o "Seating Plan {:%Y-%m-%d}.csv"

This will output a file called Seating Plan 2019-09-12.csv

Multiple Weeks

The script can output multiple weeks in advance. You can provide a number of weeks in advance with the -w or --weeks flag.

supper -w 2 # Creates three csv's. This week's, and two weeks in advance.

If datetime formatting is provided for the filename, it will give the correct datetime for that files week. Otherwise “_x” will be provided to make sure the script doesn’t overwrite itself.

Examples

supper -o "Seating Plan {:%Y-%m-%d}.csv" -w 2

Will create 3 files named

Seating Plan 2019-10-21.csv
Seating Plan 2019-10-28.csv
Seating Plan 2019-11-04.csv

---

supper -o "Seating Plan.csv" -w 2

Will create 3 files named

Seating Plan.csv
Seating Plan_1.csv
Seating Plan_2.csv

Debug

You can enable debug output using the -d or --debug flags

Known Issues

• Long events (longer than a month) may not get picked up in the script as their start dates and end dates may not be in reach of the programs search range.
• Users who do not add themselves as attendees or are not the organisers of their out of office event will not be removed from the output CSV seating plan. This is logged as warnings in the console to make you aware of these events.
• Access tokens are added where the source code is. This might cause issues if the user installs the script as root. Users should use the --user tag when installing