Omniscio

Plugin access to people's schedules

A plugin you approve can see when the people in your workspace work and when they are away, and never more than you could see yourself in Mission Control. It never sees their email addresses or roles. It is off until you turn on Plugin access to people's schedules in Settings, Labs.

On this page

What it is

A plugin can ask for one permission, shown on its install card:

Permission What it lets the plugin do
People's schedules (people.read) See when the people in your workspace work and when they are away.

It is a standard permission. A plugin that asks for it must also ask for See your workspace's people (members.read); a plugin that lists one without the other cannot be installed or published.

Where to find it

  • The switch: Settings, Labs, Plugin access to people's schedules. It starts off and hidden. While it is off, every read from a plugin is refused.
  • Review: every read a plugin makes is written to its read log, which you can review.

What a plugin can and cannot do

  • Can: list the working days and hours of the people whose hours you could see yourself: everyone when you are an admin or a project lead, otherwise only you. People with no working hours set are left out. It can also list the days people are away between two days, for everyone in the workspace: who, from which day to which day, and whether it is the whole day or half of it.
  • Cannot: see why someone is away unless it is one of your own days, or you are an admin; and never when the person chose to keep the reason private. It never sees an email address, a role, whether someone is an admin, where a day away came from, or anything it could use to change or remove one. It cannot change anything.

How it behaves

  • "Who you could see" is the same rule the Team workload panel on the People page uses, so a plugin never sees more than that panel shows you.
  • An admin can see the reason so they can tell, for example, someone who is out but still answering email from someone who is completely unavailable.
  • Names come from your workspace's member list; a day away for someone no longer on it keeps the name it was saved with.
  • When Mission Control cannot answer (for example, you are signed out), the read is refused with "Mission Control is not available." rather than an empty list, so a plugin never mistakes it for "nobody is away".
  • A plugin can make at most 60 reads a minute, shared with its other work-data reads.
  • Turning the switch off stops the very next read, with no restart.

Limits

  • A days-away read covers at most 366 days, counting both ends.
  • The member list is the first 200 people in the workspace.

Speed cost

Not measured yet. The feature adds no background work of its own (no timer, poller or watcher); it only does work when a plugin calls it, and each call is capped at 60 reads a minute. Each read asks for the member list and who you are once (the second is remembered for a minute), then makes one local database read. The off-and-on measurement in the shared Speed Cost Format needs a plugin that actually uses this permission, and is owed before the feature goes to dogfood.

Plugin access to boards and tasks and Plugin access to your inbox explain the sibling work-data permissions, Workspace members covers members.read itself, Team workload explains the People page whose rules this follows, the Plugin Marketplace page covers installing plugins and the consent card, and Plugin Developer Mode explains how a self-built plugin can use this permission before the marketplace lists it.

Last verified 2026-11-12