Career Growth
Join an Employee Resource Group with Clear Expectations About Participation and Privacy
Decide how to participate in an employee resource group by checking its purpose, time commitment and handling of member and attendee information. Two fictional invitations and a complete organizer conversation show how to choose one activity while keeping unanswered privacy questions and formal employment concerns separate.
Before joining an employee resource group, check its purpose, who can participate, how much involvement is expected and what other people can see. Ask separately about membership lists, event attendance, recordings, messages and photographs. A welcoming group or a request to keep discussions private does not establish that membership is confidential.
You can start with one suitable activity and decide later whether to join a channel, volunteer or take a leadership role. This LandOffer.ai guide uses two fictional event descriptions and a completed organizer conversation to make that decision concrete. No membership, employer account or privacy setting was tested or changed.

Identify the kind of support you want
An employee resource group, often called an ERG, may offer community, shared learning, awareness events or opportunities to contribute to workplace inclusion. Read the group's current purpose rather than assuming every group offers the same services. Decide whether you want an introduction to colleagues, practical information, peer conversation or an organizing role.
Set a modest first goal: “Meet colleagues who understand caregiving schedules and learn where the organization's published resources are.” A different goal, such as resolving a disputed leave decision, requires identifying the appropriate employer process. Attending an ERG does not itself submit a request or start a formal review.
For example, Georgetown's public guidelines describe voluntary, employee-led groups and direct individual employment concerns to appropriate university offices. This is Georgetown's stated structure, not a rule that determines every employer's ERG responsibilities. Georgetown guidelines.
The distinction matters even when a group leader is helpful. A colleague might explain where a policy lives without having authority to interpret your eligibility, change your work arrangement or investigate a concern. Ask what the person can actually do before sharing details they do not need.
Check participation rules for the specific activity
Find the current charter or group page and the actual event invitation. Confirm employee or contractor eligibility, whether allies may attend, whether registration creates membership and whether listening without speaking is acceptable. A general welcome page may not describe a particular small discussion or volunteer assignment.
GitLab's public guide, for instance, distinguishes resource and advocacy groups, lists live and asynchronous participation routes, and says activities welcome members and allies unless specifically labelled members-only. Those are GitLab arrangements. Check your own organization's rules rather than copying eligibility assumptions from another employer. GitLab group guide.
Separate ordinary participation from additional commitments. Attending a session is different from joining a mailing list, moderating a channel, collecting feedback or leading a group. Ask whether the next step is optional and what work it entails. You can support a group's purpose without accepting a recurring administrative job. Naming that boundary makes it easier to offer help you can actually finish.
Also clarify work time. Check the relevant policy and any scheduling or approval process for your role. Do not assume a volunteer-led event is automatically paid time, automatically unpaid or exempt from coverage responsibilities. Make a realistic plan without turning a personal explanation into the price of participation.
Treat privacy as several concrete questions
“Is this private?” often produces an answer that is too broad to use. Ask who can access each record: a group roster, registration response, calendar guest list, chat history, meeting recording, transcript, photograph or organizer's notes. Membership and attendance are separate records. You might attend without joining, or remain on a mailing list after skipping every event. Declining a photograph does not remove either record.
Ask what the group controls and what the employer's systems retain. GitLab's Team Member Privacy Policy is one employer example that describes monitoring of company resources, subject to applicable restrictions and local requirements. It does not establish what another employer can access or how a particular ERG is configured. Read your current employer notice and ask the responsible team about unanswered questions. GitLab privacy policy.
A facilitator can request that participants not repeat personal stories. That is a conduct expectation, not proof that nobody will disclose them or that no administrative access exists. Likewise, “not recorded” does not answer whether registration names, chat or notes remain. Avoid filling these gaps with either absolute reassurance or an assumption of unrestricted access.
You do not need to explain a private identity or family circumstance simply to ask how a group handles attendance. Describe the information boundary you need: “Before registering, I want to know whether my name appears in a directory and whether the session creates a transcript.”
Worked asset one: compare two invitations before joining
The following organization, people, events and records are entirely fictional. Aven employee Mika wants an introduction to the Caregiving Connections group and published resources, without discussing personal circumstances. Mika has arranged up to 60 minutes of participation time this month through Aven's ordinary scheduling process; this does not confer a general benefit or future approval.
Organizer Ottilie sends two descriptions. Neither requires a personal story, and both accept employees and allies under Aven's fictional group rules.
Activity A: resource orientation. A 30-minute session explains where to find Aven's published resource pages. A presenter-only recording will be placed on the employee intranet. Attendees are instructed not to put individual cases in chat. Registration is optional for receiving the presentation link; joining the group's continuing mailing list is a separate choice. The invitation initially says nothing about attendee names or chat retention.
Activity B: peer roundtable. A 45-minute monthly conversation invites participants to exchange experiences. It is described as unrecorded, with a request not to repeat others' stories. Registration uses work email. The invitation says the organizer keeps a roster but does not identify who can view it or when it is removed. Attendance does not require volunteering or speaking.
| Decision question | Activity A assessment | Activity B assessment |
|---|---|---|
| Fit with Mika's immediate purpose | Strong: introductory resource navigation without a personal case | Possible later: experience exchange is beyond the current goal |
| Estimated total time | 30-minute session, 10-minute preparation, five-minute review: 45 minutes | 45-minute session, 15-minute optional preparation Mika would choose, 10-minute review: 70 minutes |
| Known visibility | Presenter recording will be available internally; attendance and chat handling need clarification | Work-email registration and organizer roster exist; recording is stated to be off |
| What remains unanswered | Who sees attendees; whether chat enters the recording; how long registration is retained | Roster access and retention; how discussion notes and reporting are handled |
| Initial decision | Suitable if participation visibility is acceptable after clarification | Defer: exceeds this month's planned time and leaves important roster questions open |
Mika does not label A confidential or B unsafe. The descriptions support different purposes and leave different gaps. A small discussion can create an identifiable registration record, while a broadly available presentation may require little personal disclosure. Neither format alone proves confidentiality or anonymity. The right choice depends on the activity and your boundary, not just its size.
The estimates are Mika's planning assumptions, not attendance requirements imposed by the group. Activity A leaves 15 minutes within the agreed 60-minute allowance; both activities together would require 115 minutes, exceeding it by 55. Mika makes no commitment to attend both or to provide unpaid follow-up work.
Worked asset two: a completed boundary conversation
Mika asks Ottilie the following questions before registering. The answers are authored for this example, not verified settings in a real collaboration platform.
Mika: “Can I attend the orientation without joining the mailing list or explaining why this topic matters to me?”
Ottilie: “Yes. You can use the event link without ongoing membership. Mailing-list enrolment is separate, and personal introductions are optional. We will not ask you to describe your caregiving circumstances.”
Mika: “Will other attendees see my name? Does the recording include the audience or chat?”
Ottilie: “People in the live meeting can see participants' display names. The event plan calls for recording the presenter and slides, not the participant gallery. The host must check that setup before the session; this description is not a verified platform test. We will not include chat in the published recording. That does not make attendance anonymous; platform attendance records may still exist.”
Mika: “Who keeps those records, and does declining a photograph remove them?”
Ottilie: “We are not taking attendee photographs at this event. Our event list is available to the two organizers, me and Soren. That describes our intended event administration; it does not establish that platform administrators have no access. I cannot confirm the platform's administrative retention period. The workplace privacy team owns that question; not taking photographs does not remove meeting records.”
Mika: “For the roundtable, can you promise that what someone shares will remain confidential?”
Ottilie: “We ask people not to repeat others' stories and do not plan a recording. I cannot guarantee other participants' conduct or promise that organizational policies never require information to be shared. I will obtain the current escalation guidance before describing those boundaries. Please do not treat the group as an anonymous reporting channel.”
Mika: “I will choose the orientation with those limits. Please do not add me to the ongoing mailing list. I will hold the roundtable decision until its roster and escalation arrangements are clearer.”
Ottilie: “Understood. The orientation is separate from mailing-list membership. I will provide the current privacy contact and clarify the roundtable information; I will not treat your question as consent to join.”
Completed participation record
Mika's private planning note reads: “Choose Activity A only, with 45 minutes reserved in total. Live attendees may see my display name; I accept that visibility for this introductory event. No personal case will be shared. Mailing-list membership and Activity B remain unchosen. Administrative record retention is unresolved; I have requested the relevant policy contact, not assumed deletion. Recheck if the organizer changes the recording plan. If the setup differs at the event, I can leave rather than disclose more than I intended.”
That is a completed decision within the fictional scenario, not an actual registration or an assurance that these controls work. Mika has accepted a known level of visibility for one activity while retaining an unresolved question. Someone who requires anonymity could reasonably defer that same activity instead.

Participate without becoming the group's representative
If you join, listen to the group's purpose and follow the stated discussion agreements. Ask before quoting another person, forwarding a thread, taking a photograph or putting someone's story in a team presentation. Access to a conversation does not make its contents yours to redistribute.
Being an ally does not require claiming someone else's experience or offering answers you are not qualified to give. Ask how you can help with a specific task and state your available time. If you volunteer for an event, agree the output, owner and end date rather than accepting an indefinite expectation to organize future sessions.
Avoid treating any participant as the spokesperson for a whole identity or experience. You can describe what you learned from an event without naming who disclosed it or claiming the group endorses your interpretation. An executive sponsor's presence also does not mean every discussion becomes a decision or an individual concern has been addressed.
Keep formal needs on the appropriate route
If your need changes from community to an individual employment issue, find the current official process for that issue. Ask about the receiving office's role, information handling and next step before submitting sensitive details. A peer can point you to a route; that is different from a confirmed submission or resolution.
Do not delay an applicable required process while waiting for the next group meeting. Equally, do not assume that mentioning an issue in a group automatically creates the formal record you intended. This guide does not determine legal reporting duties, deadlines or confidentiality protections for a particular situation.
Review your participation after the first activity: did it serve your purpose, was the time sustainable, and were the information boundaries clear enough? You may continue, choose another format, decline extra responsibilities or step back using the organization's process. Choose a next step you understand rather than treating joining as a promise of belonging, career advancement or privacy. More practical current-work guides are available from LandOffer.ai.
Sources and Further Reading
- Georgetown: Guidelines for Employee Resource Groups, no exact publication date displayed; checked October 27, 2026. Voluntary participation, purpose and routes for individual concerns at that institution.
- GitLab: Team Member Resource and Advocacy Group Guide, last modified July 20, 2026. Organization-specific membership, allies and participation formats.
- GitLab: Team Member Privacy Policy, policy last updated December 12, 2025; current body checked October 27, 2026. Employer-specific information handling; no conclusions about another employer's legal obligations or system settings.


