Googleカレンダーの権限: what the free tier covers

Searching for the cost of Google Calendar permissions turns up a pricing page with no line item for permissions on it. That absence is the answer, but it is an unhelpful way to receive it, because the real question underneath is usually narrower: something about sharing is not working the way it should, and it is worth knowing whether money is any part of the fix.

In almost every case it is not. Setting who can see a calendar, and what they can do with it, costs nothing on a free Google account, at every level the system offers. What a paid subscription adds is a layer above the individual: the ability to set limits that individuals cannot exceed and defaults that individuals inherit. That distinction, capability versus control, is where the money line actually falls, and it decides whether a subscription would solve a given problem or leave it exactly as it is.

Every sharing level is free

A free Google account can create additional calendars, share any of them with named people or groups, and assign each one of the five access levels Google documents: see only free/busy with details hidden, see event details, make changes with private events shown as free/busy, make changes and see event details, and make changes and manage sharing.

Nothing on that list is gated behind a subscription. A paid plan does not unlock a sixth level, and it does not change what any of the five mean. Per-event guest controls are the same too: allowing guests to modify an event, to invite others, or to see the guest list works identically on a free account. Marking an event private, publishing a calendar to the public, and generating a secret address in iCal format are all available at no cost.

This matters because a sharing problem on a personal account is never a billing problem. If a colleague cannot see a calendar, the cause is the level chosen, an invitation that was never accepted, or an event-level setting. Upgrading would change none of those. The most expensive outcome here is paying for a subscription and finding the symptom unchanged, which happens often enough to be worth ruling out first.

What the paid layer actually adds

Google Workspace introduces an administrator, and an administrator can do things no individual account holder can do at any price.

The first is a ceiling on external sharing. An administrator chooses one of four limits for the organization: only free/busy information with event details hidden, share all information but outsiders cannot change calendars, share all information and outsiders can change calendars, or share all information and allow managing of calendars. Whatever an individual selects, the result is clipped to that ceiling on its way outside the organization. This is the only mechanism that makes a statement like "meeting titles never leave this company" structurally true rather than a matter of everyone remembering.

The second is a default for internal sharing: no sharing, only free/busy information, or share all information. Defaults apply to new calendars and to existing ones the user has not customized, which means a new hire who configures nothing still lands in a known state. On a group of free accounts, the equivalent is instructions and follow-up.

The third is resource calendars. Meeting rooms, equipment and other bookable things exist as calendar objects that an administrator creates, and their availability shows up during scheduling. For anyone whose real problem is back-to-back meetings in different rooms or buildings, this is a scheduling feature rather than a permission feature, and it is only available on the paid side.

The published prices, and the conditions attached

The figures below are the per-user monthly prices published for Japan, in yen, before tax.

Edition	Per user, per month
Business Starter	800 yen
Business Standard	1,600 yen
Business Plus	2,500 yen
Enterprise	Contact sales

Three conditions sit around those numbers and change what an organization actually pays.

The prices assume a one year commitment. Google advertises a 16 percent saving for committing to a year. A plan without that commitment costs more per user per month, and the difference is worth calculating against how likely the headcount is to move.

Introductory pricing is narrower than it looks. The discounted rate shown to new customers applies to the first 20 users added and lasts 12 months. Users beyond that count, and the period after it, are billed at the standard rate. An organization of 30 people estimating an annual figure from the introductory price will be wrong.

Starter, Standard and Plus cap at 300 users. Above that, Enterprise is the only option and pricing moves to a quote. Plans also include a 14 day trial, which is enough time to test the thing that actually matters: whether tightening the external sharing ceiling breaks how the organization currently schedules with people outside it.

For permission control specifically, the entry edition is sufficient. Both the external ceiling and the internal default are available on Business Starter. The higher editions add recording and larger meetings, eDiscovery, Vault retention, secure LDAP and advanced endpoint management, none of which change what calendar sharing can express.

What more money does not add

Several things stay exactly the same regardless of which edition is in use, and knowing them shortens the decision.

Acceptance is still required. Somebody outside the organization has to click the link in the invitation email before a shared calendar appears in their list. No edition removes that step.

The five levels remain five. Requirements like "let this person edit only the client meetings" or "let this person see titles but not descriptions" have no setting at any price. They are expressed by splitting events across calendars and sharing those calendars differently, which is the same technique on a free account as on a paid one.

Storage is a separate axis entirely. The pooled storage per person rises sharply between editions, from 30 GB on Business Starter to 2 TB on Business Standard and 5 TB on Business Plus. That figure covers mail and files. It has no relationship to how many calendars exist or which permission levels can be chosen, and a large number in that column is not a reason to move up if the problem being solved is about access.

Application programming interface access follows the same rule. Scopes for reading calendars, writing events, and changing sharing settings exist on both free and paid accounts, and which of them work is decided by what the account can already reach. A calendar that is not shared with an account cannot be read by any scope that account requests.

The arithmetic that decides it

Because the entry edition covers the permission controls, the calculation is simple and depends almost entirely on headcount. Twelve people on Business Starter is 9,600 yen per month and 115,200 yen per year. The same twelve on Business Standard is 19,200 yen per month, but the difference between those two figures buys meeting recording and storage rather than anything related to sharing.

Set that against what it replaces. On free accounts, the equivalent of a ceiling is a written policy plus periodic checking, and the equivalent of a default is instructions given to every new person. Both work until somebody is busy. The question is not whether the controls are worth having, but whether the cost of the thing they prevent, a client name visible in a shared meeting title, an ex-contractor still holding access, is larger than a five figure annual number for a small team.

For a single person managing several calendars and sharing with a handful of collaborators, the honest answer is usually no. There is no ceiling to enforce and no default to standardize when the only person configuring anything is the one who would also be enforcing the policy.

Signals that the free side has run out

Rather than comparing feature lists, it is quicker to check whether any of the following is already true. Each one describes a job that free accounts cannot do at all, as opposed to one they can do with more effort.

Calendars are shared outside the organization as a matter of routine, by people who were never briefed on what the levels mean. Effort does not fix this, because the failure happens on the days nobody is thinking about it. A ceiling does.

Something in writing, a contract clause, a client requirement, an internal policy, states what may and may not leave the company. A policy with no mechanism behind it is a description of intentions. The external sharing limit is the mechanism that makes the statement checkable.

People join and leave often enough that first-day configuration is a recurring cost. An internal default applies to new calendars automatically, and to existing calendars the user has not customized, so the starting state is known without anybody being told anything.

Rooms, desks or equipment need to be booked alongside meetings. There is no free equivalent. Resource calendars are created by an administrator and exist only on the paid side.

Somebody has to be able to answer who has access to what without opening every calendar individually. Administrative visibility is the difference between that being a question and being a project.

If none of those apply, the free tier is not a compromise. It is the correct configuration, and the remaining friction is somewhere other than access.

Where the cost actually sits for one person

If a subscription would not change anything, the remaining costs are on the client side, and they follow a different shape.

Desktop calendar applications for Mac are sold two ways: a recurring subscription, or a single purchase that keeps working. Which is cheaper depends entirely on how many years the tool stays in use, and the crossover is usually somewhere between the second and third year. That makes the decision less about the headline figure and more about whether the thing being bought is expected to last. Terms and the conditions attached to them differ by product, and the ones for this one are set out under Buy, which is enough to run the same calculation against a personal number of years.

The features worth paying for in that layer are not permission features at all. They are about how many calendars from how many accounts fit in one view, how many steps an event takes to create, and whether gaps between meetings account for getting from one place to the next. The differences between the available approaches are laid out in Compared with other calendars, and recurring questions about what is and is not included are collected in the FAQ.

What to change first

Before pricing anything, confirm that the problem is not an unaccepted invitation, a level set one step too low, or an event-level setting on a single meeting, since none of those cost money to fix. If the problem genuinely is that individual choices need a limit above them, the entry Workspace edition is where that limit lives, and Caltimate covers the other half, which is what happens on the Mac after the access question is settled.