Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Define policy for instructlab.ai Google account usage #301

Open
russellb opened this issue May 31, 2024 · 3 comments
Open

Define policy for instructlab.ai Google account usage #301

russellb opened this issue May 31, 2024 · 3 comments
Assignees
Labels

Comments

@russellb
Copy link
Member

I noticed several individuals listed on a meeting invite on the community calendar using [email protected] addresses. My understanding is that these accounts exist as necessary to manage the instructlab.ai Google workspace.

I suggest a policy is needed for how these accounts are managed. I see two options:

Option 1:

  • Create a policy that clarifies that these accounts are for Google Workspace administration purposes only and not to be used otherwise (not for individual email, calendar, etc purposes)

Option 2:

  • Create a policy that clarifies who is eligible to get an account
  • Define the procedure for requesting an account under that eligibility
  • Write down any expectations on limitations of their use (general purpose personal email presumably out of scope, for example)
@cybette cybette self-assigned this May 31, 2024
@lhawthorn
Copy link
Member

This is a great point and the truth is option 1, but we should document it. Tangentially related to this is #223

@wking
Copy link
Contributor

wking commented Jun 4, 2024

Tangentially related to who can post as group. These docs point out "post as group" means "posting messages from the group’s email address", and I expect this issue is more about [email protected], and not [email protected], but both touch on sending email from @instructlab.ai, so possibly worth some cross-refs or something in any docs landed to address this issue.

Copy link
Contributor

This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.

@github-actions github-actions bot added the stale label Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants