Skip to content

Organisers being added to the Google Workspace #104

@carvingpumpkins

Description

@carvingpumpkins

Summary

As I understand it, codebar has a Google Workspace through the non-profit scheme that they offer. If possible, I think it would be beneficial for each organiser to have an account created in the workspace as part of onboarding.

Benefits

Organisers without access to the workspace are more likely to store coach/student information in unmanaged platforms which could lead to data loss and/or data protection issues. Managed access to the workspace would reduce the likelihood of this by providing a secure place to store potentially sensitive information. Furthermore, it would prevent organisers from having to use their own/create new email addresses, thus keeping organiser communications limited to the workspace and further aligning with good data protection practices.

Setbacks

There could be not-insignificant admin overhead involved in setting up onboarding/offboarding procedures. I'm not aware of the current process of managing active/inactive organisers but this might need to be put in place to ensure old accounts are deleted. Other considerations could be ensuring accounts only have the access they need when it comes to files stored in Drive.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions