Skip to content
DERequest a demo

RIDIAN FOR TEAMS

Connected calendars. Protected details.

Work, clients, personal life: your calendars are part of the same day. Ridian brings availability together, with clear rules for the details that travel with it.

Request a demo

An individual offer. A starting point agreed together.

One day. Two calendars.Example
Personal · Google
09:00
10:00 – 11:00Personal appointmentDetails stay here
12:00
Work · Microsoft
09:00
10:00 – 11:00BusyAvailability only
12:00
Personal → WorkTitle and details hidden
Conceptual example. Each direction has its own sharing rules.

SHARE AVAILABILITY

Your team sees that you’re busy. Not why.

A personal event can appear as “Busy” in your work calendar, leaving its title and other details behind. In the other direction, organisation policy limits which work information can be shared.

  • Accounts stay with their respective users.
  • Rules apply to each direction of sharing.
  • Selected calendars are connected, with no blanket account access.

From calendar friction to clear rules.

  1. Define the use case

    Which accounts need to work together? What information do your people actually need?

  2. Agree the boundaries

    We review your organisation’s policies and individual calendar permissions together.

  3. Start with your team

    Validate the agreed workflow with selected users before expanding the rollout.

CONTROL IS PART OF THE CONNECTION

You define what gets shared.

A connected account is not unrestricted access. User consent, provider permissions and organisation policy work together to determine permitted actions.

Explore security and data flows
RIDIAN / CONNECTWith clear boundaries
Google
Microsoft
Apple iCloud
Ridian
Teams
Your productPilot planned
One shared permission foundation
User consentProvider permissionsOrganisation policy
Connection model · Capabilities vary by access method

ONE CONNECTION. MORE POSSIBILITIES.

The working day goes beyond the calendar.

Sync calendars and get more done through authorised assistants: events, rooms, tasks, contacts and outgoing email. Each capability has its own permissions.

Keep calendars connected

Make availability visible across your calendars. You decide which details are shared in each direction.

Google · Microsoft · supported CalDAV providers

Find time. Plan the next step.

Check free time, create and update events or respond to invitations using the calendars you have allowed.

Google · Microsoft / assistant access

Find a room that fits

Find organisation rooms by capacity and availability, then request one through an event. The room’s policy determines acceptance.

Google Workspace · Microsoft / admin permissions required

Move tasks forward

Read, create, update, complete and delete tasks directly in Google Tasks or Microsoft To Do.

Google · Microsoft / separately authorised

Keep contacts within reach

Find, read, create and update personal contacts, so the right details are ready for your next step.

Google · Microsoft / separately authorised

Send email deliberately

Send a plain-text email when you explicitly ask. Without inbox access, drafts or attachments.

Google · Microsoft / sending only

Assistant capabilities use MCP and depend on provider permissions, organisation policy and the client. The planned developer pilot has a separate, calendar-only scope.

Inside the assistant you use.

Connect Ridian to ChatGPT or Claude through a custom MCP connector. Setup and available actions depend on your client and its settings.

ChatGPTClaude
Explore integrations

Before your first connection.

Does everyone have to switch calendar providers?

No. Ridian connects existing Google, Microsoft and supported CalDAV calendars. We use the demo to identify the combination and permissions that fit your use case.

Can administrators see personal calendars?

An organisation role does not grant blanket access to personal calendars. Users connect their own accounts; organisation policy limits the sharing of work data.

Can we connect assistants too?

Ridian offers MCP access for assistants. It uses connected accounts and checks the relevant permissions. Available actions depend on the provider, granted access and the assistant you use.

What happens when I request a demo?

Tell us about your calendar setup and what you want to achieve. We arrange a time and show a relevant workflow. Your request is not a confirmed booking or a contract.

How do your calendars work together today?

Tell us about your use case. We’ll discuss providers, permissions and a suitable starting point for your team.

Request a demo