Google Apps Administration Policy - Revision history

Adam.burgess at 03:50, 18 April 2025

2025-04-18T03:50:07Z

← Older revision		Revision as of 03:50, 18 April 2025
Line 1:		Line 1:
			*draft*


	Effective date of the policy and date of any revisions		Effective date of the policy and date of any revisions

Adam.burgess: /* Policy */

2025-04-13T03:01:14Z

Policy

← Older revision		Revision as of 03:01, 13 April 2025
Line 29:		Line 29:

	== Policy ==		== Policy ==
	# 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 board members who ~~remain~~ in a volunteer capacity).		# 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).
	# 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.		# 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.
	# 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.		# 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.

Adam.burgess: /* Policy */

2025-04-13T03:00:45Z

Policy

← Older revision		Revision as of 03:00, 13 April 2025
Line 29:		Line 29:

	== Policy ==		== Policy ==
	# The set of individuals with super admin access at any one time should consist of 1-2 staff members ~~and 1-2~~ board members.		# 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 board members who remain in a volunteer capacity).
	# 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.		# 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.
	# 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.		# 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.

Adam.burgess: /* Implementation and Monitoring */

2025-04-12T20:16:30Z

Implementation and Monitoring

← Older revision		Revision as of 20:16, 12 April 2025
Line 36:		Line 36:

	== Implementation and Monitoring ==		== Implementation and Monitoring ==
	~~# Each director, officer, employee and key program volunteer shall be provided with and asked to review a copy of this Policy and to acknowledge in writing that he or she has done so~~
	# Annually each director, officer, employee and key program volunteers shall complete a [http://edmontonbikes.ca/w/images/e/ea/EBC_Conflict_of_Interest_Policy_form.pdf disclosure form] identifying any relationships, positions or circumstances in which s/he is involved that he or she believes could contribute to a Conflict of Interest. Such relationships, positions or circumstances might include service as a director of or consultant to another nonprofit organization, or ownership of a business that might provide goods or services to Bike Edmonton. Any such information regarding the business interests of a director, officer, employee or volunteer, or a Family Member thereof, shall be treated as confidential and shall generally be made available only to the Chair, the Executive Director, and any committee appointed to address Conflicts of Interest, except to the extent additional disclosure is necessary in connection with the implementation of this Policy.
	~~# Regular Bike Edmonton volunteers will be provided with the conflict of interest policy during their volunteer orientation but will not be required to complete annual disclosures.~~
	~~# This policy shall be '''reviewed annually''' by each member of the Board of Directors.~~
	~~## Any changes to the policy shall be communicated to all staff and volunteers.~~

	== Policy Approval Date & Review Date ==		== Policy Approval Date & Review Date ==

Adam.burgess: /* Policy */

2025-04-12T20:16:11Z

Policy

← Older revision		Revision as of 20:16, 12 April 2025
Line 29:		Line 29:

	== Policy ==		== Policy ==
			# The set of individuals with super admin access at any one time should consist of 1-2 staff members and 1-2 board members.
			# 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.
			# 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.
			# Stripped of access-
			# Those with access are responsible for implementing; the board is responsible for approving...

	== Implementation and Monitoring ==		== Implementation and Monitoring ==

Adam.burgess at 20:08, 12 April 2025

2025-04-12T20:08:25Z

← Older revision		Revision as of 20:08, 12 April 2025
Line 15:		Line 15:
	# To define the distribution and succession of Google Apps "super admin" privileges.		# To define the distribution and succession of Google Apps "super admin" privileges.

	= Philosophy ==		== Philosophy ==
	# 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.		# 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.
	# It is recognized that a larger data management policy might be desirable, however this policy is designed to be specific, limited, clear, and actionable.		# It is recognized that a larger data management policy might be desirable, however this policy is designed to be specific, limited, clear, and actionable.

Adam.burgess at 20:07, 12 April 2025

2025-04-12T20:07:36Z

← Older revision		Revision as of 20:07, 12 April 2025
Line 8:		Line 8:
	Scope of Permissible Exceptions		Scope of Permissible Exceptions
	Positions in the organization responsible for implementing and monitoring the policy		Positions in the organization responsible for implementing and monitoring the policy




			== Purpose ==
			# To define the distribution and succession of Google Apps "super admin" privileges.

			= Philosophy ==
			# 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.
			# 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 ==
			# By necessity, this policy applies to those with current super admin access, who therefore have the ability and responsibility for distributing future access.

			== Definitions ==
			#
			#
			#


			== Policy ==

			== Implementation and Monitoring ==
			# Each director, officer, employee and key program volunteer shall be provided with and asked to review a copy of this Policy and to acknowledge in writing that he or she has done so
			# Annually each director, officer, employee and key program volunteers shall complete a [http://edmontonbikes.ca/w/images/e/ea/EBC_Conflict_of_Interest_Policy_form.pdf disclosure form] identifying any relationships, positions or circumstances in which s/he is involved that he or she believes could contribute to a Conflict of Interest. Such relationships, positions or circumstances might include service as a director of or consultant to another nonprofit organization, or ownership of a business that might provide goods or services to Bike Edmonton. Any such information regarding the business interests of a director, officer, employee or volunteer, or a Family Member thereof, shall be treated as confidential and shall generally be made available only to the Chair, the Executive Director, and any committee appointed to address Conflicts of Interest, except to the extent additional disclosure is necessary in connection with the implementation of this Policy.
			# Regular Bike Edmonton volunteers will be provided with the conflict of interest policy during their volunteer orientation but will not be required to complete annual disclosures.
			# This policy shall be '''reviewed annually''' by each member of the Board of Directors.
			## Any changes to the policy shall be communicated to all staff and volunteers.

			== Policy Approval Date & Review Date ==

Adam.burgess: Created page with " 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"

2025-04-12T19:55:30Z

Created page with " 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"

New page

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