Rules for Meeting Subscriptions

Rules

Rules are a lightweight way to add user authorization to a Meeting Subscription.

Example

Given a user named Darwin:

[{
    "first_name": "Darwin",
    "last_name": "Stoppelman",
    "metadata": {"department":"A"}
}]

and a user named Hammy:

[{
    "first_name": "Hammy",
    "last_name": "Stoppelman",
    "metadata": {"department":"B"}
}]

and a Meeting Subscription without Rules called the Yelp Weekly, both Hammy and Darwin would be able to see the subscription on their profile page.

However, if we wanted to set up a Meeting Subscription for only employees in department A, we could add a Rule to our Meeting Description with name="department" and value="A". In this case, only Hammy would see the Yelp Weekly subscription upon log in.

You may have one or many Rules for a Meeting Subscription. The admin must also set the rule_logic. If there are many rules, is just one of them being true good enough (any)? Or, do you need them all to be true to be valid (all)?

Using the example above, we can add another rule with name="department" and value="B". Using any for rule_logic means that both Hammy and Darwin will see the Yelp Weekly, but someone in department C would not. If the rule is set to all, neither Hammy or Darwin would see the "Yelp Weekly" because they are not both in department A and department B.

A practical use-case for all would be a company that has many offices and many departments. Here you could specify that the meetings can only be seen by employees in the SF building who are also in the Sales Department.