# Google Workspace

> Sync deadlines to Google Calendar and attach files from Drive without consuming workspace storage.

> For the complete documentation index, see [llms.txt](https://helpdesk.orangescrum.com/llms.txt).

Source: https://helpdesk.orangescrum.com/guide/cloud/integrations/google-workspace

---
> **Pro and Premium**
>
> Google Calendar and Drive integrations require Pro Unlimited or above.

## Google Calendar

Pushes Orangescrum dates into Google Calendar so deadlines sit alongside
meetings — which is where most people actually look.

**Connect your Google account**

    From your profile or project settings. You will be asked to grant calendar
    access.

**Choose what syncs**

    Your assigned task due dates, project milestones, and sprint dates.

**Pick a target calendar**

    Use a **separate calendar**, not your primary one. You can then toggle it
    off during a focused week without losing your meetings.

> **Sync everything and you will read nothing**
>
> Forty task entries a day buries your actual meetings, and people respond by
> hiding the calendar entirely — including the deadlines that mattered. Sync
> your own due dates and project milestones. Nothing else.

### Direction

Sync runs **from Orangescrum to Google**. Editing an event in Google does not
move the task — change the date in Orangescrum.

## Google Drive

Attach Drive files to tasks by link rather than uploading a copy.

- **Link from Drive**: Doesn't count against [storage](https://helpdesk.orangescrum.com/guide/cloud/plans/plans-and-limits). Always the current version. Drive permissions apply.

- **Upload directly**: Counts against storage. A frozen snapshot. Orangescrum permissions apply.

Link for living documents — specs, designs, sheets people keep editing. Upload
for point-in-time evidence: a screenshot of a bug, a signed-off document.

> **Drive permissions are separate**
>
> A linked file is only visible to people who have access **in Drive**. Someone
> can be a project member and still hit "request access". Check sharing when you
> link something the whole team needs.

## Google sign-in

Sign in with a Google account instead of a password. Distinct from full
[SSO](https://helpdesk.orangescrum.com/guide/cloud/admin/security), which is Premium and enforces
organisation-wide identity policy.

## Connecting well

**Grant the narrowest scope**

    Calendar access does not require Drive access. Only grant what you use.

**Connect per person for calendar**

    Calendar sync is personal — each user connects their own account.

**Review connections periodically**

    Disconnect what nobody uses.

## Troubleshooting

**Calendar events stopped appearing**

    The Google authorisation expired or was revoked — often when a workspace
    admin changes app access policy. Reconnect.

**Events are on the wrong calendar**

    Change the target in the integration settings. Existing events do not move;
    they will need clearing manually.

**Colleagues can't open a linked Drive file**

    Drive sharing, not Orangescrum permissions. Share the file or the containing
    folder with the team.

**Deleted a task but the calendar event remains**

    Deletions do not always propagate. Remove the event in Google.

- [Project calendar](https://helpdesk.orangescrum.com/guide/cloud/views/calendar): The in-product calendar view.

- [All integrations](https://helpdesk.orangescrum.com/guide/cloud/integrations/overview): What else you can connect.