Google Apps Administration Policy

• • • draft***

Effective date of the policy and date of any revisions Purpose of the policy Philosophy Policy Statement Definitions of any key concepts or terms used in the policy Scope Scope of Permissible Exceptions Positions in the organization responsible for implementing and monitoring the policy

Purpose

1. To define the distribution and succession of Google Apps "super admin" privileges.

Philosophy

1. Access should be liberal enough to be useful, but restrictive enough to maintain security and confidentiality. The distribution of access should recognise that Bike Edmonton consists of an ever-shifting group of staff and volunteers, most of them part-time, with a variety of strengths and interests.
2. It is recognized that a larger data management policy might be desirable, however this policy is designed to be specific, limited, clear, and actionable.

Scope

1. By necessity, this policy applies to those with current super admin access, who therefore have the ability and responsibility for distributing future access.

Policy

1. The set of individuals with super admin access at any one time should consist of 2-3 staff members, board members, or volunteers (for example, recent staff or board members who continue in a volunteer capacity).
2. Individuals selected should be reliable, security-conscious, available to utilise their access when needed, and intending to stay involved with Bike Edmonton for an extended period of time.
3. The composition of this group should be changed as little as possible, i.e. it should not automatically be reassessed when there are staffing or board changes. It should be reassessed when anyone with current access leaves the organisation, wishes to stop being a super admin, or is stripped of their access.
4. Stripped of access-
5. Those with access are responsible for implementing; the board is responsible for approving...