import { z } from 'zod';
/**
 * The level of access an access control rule grants to its scope, from no
 * access at all up to manager access over the calendar's own sharing.
 *
 * `writer` and `writerWithoutPrivateAccess` differ on two axes. The latter
 * reads and writes only the events that are not private, seeing private ones
 * as opaque busy blocks, so it is a narrower grant than its name suggests:
 * the restriction is on writing as well as reading. Only `writer`
 * additionally carries read access to the calendar's own ACLs, which is why
 * listing a calendar's rules needs `writer` or `owner` and a `reader` grant is
 * not enough. `owner` is the escalation to watch, carrying every
 * `writer` permission plus the ability to modify other users' access levels,
 * so a rule granting it hands over control of the calendar's sharing. It is
 * distinct from the calendar's data owner, of which there is exactly one.
 *
 * Ordered least to most access, and sourced from the discovery document
 * rather than the bundled client types, which omit
 * `writerWithoutPrivateAccess`.
 *
 * @see https://developers.google.com/workspace/calendar/api/concepts/sharing
 */
export declare const AclRole: z.ZodEnum<{
    freeBusyReader: "freeBusyReader";
    none: "none";
    owner: "owner";
    reader: "reader";
    writer: "writer";
    writerWithoutPrivateAccess: "writerWithoutPrivateAccess";
}>;
export type AclRole = z.infer<typeof AclRole>;
//# sourceMappingURL=AclRole.d.ts.map