Groups and hosts

Set group and organization privacy

Privacy settings help you decide what people outside your admin team can see. They are especially important before you share a public profile, accept Marketplace interest, or invite people into a shared workspace.

Best forGroup and host admins
ControlsVisibility and sharing
Review beforePublic profiles and invites

Quick path

  1. Open the group or host organization you manage.
  2. Go to its settings.
  3. Review whether the profile or gig activity should be public, limited, or private.
  4. Choose whether non-admins can see members or connected groups.
  5. Choose whether pay should be visible to non-admins when that setting is available.
  6. Review invite and Marketplace behavior before sharing links or accepting outside interest.
  7. Save changes and check the public-facing pages if you use them.

Start with public versus private

A public setting helps people find or understand the group or organization. A private setting keeps more of the work inside the people who already belong there.

Neither choice is automatically better. A wedding band, venue, or contractor roster may want public discovery. A private worship team or internal event crew may prefer less visibility.

ChoiceGood fit
More publicYou want people to find the group or host, view public details, or understand what kind of gigs you handle.
More privateYou mainly use Gigditty for internal planning, roster history, invitations, and shared records.

Decide who can see people and groups

Some settings control whether non-admins can see member lists or connected group lists. This matters when you have substitutes, contractors, private rosters, or internal teams.

If the list helps people understand the organization, showing it may be useful. If it exposes private relationships, keep it limited.

  • Show members when the roster is meant to be visible and useful.
  • Hide members when the roster includes private, temporary, or sensitive relationships.
  • Show connected groups only when that helps non-admins understand the host organization.
  • Review these choices after big roster changes.

Understand gig visibility

Gig visibility affects what non-invited people can understand about a group or host's events. It is separate from private details inside the gig.

When you import or create gigs for a group or host, the visibility setting can change how the event is described to people who are not directly invited.

Public does not mean everything. Public-facing gig details should not expose private notes, internal comments, private contact information, or payment details unless a setting clearly allows that.

Review pay visibility carefully

Pay visibility settings deserve extra attention. Some groups and hosts want pay to be transparent to the people involved. Others need pay details limited to admins and invited members.

Before changing this setting, think about expectations in your group, the sensitivity of the information, and who truly needs to see it.

  • Keep pay private when the details are sensitive or still being negotiated.
  • Show pay only when it supports clear expectations and matches your group's policy.
  • Update gig-specific pay details when an agreement changes.

Check privacy before sharing

Before you share a public profile, send invite links, post openings, or promote a gig, review the settings that shape what people can see.

This is a good habit for any admin team. It prevents surprises and makes shared links easier to trust.

  • Look at the profile or public page the way an outsider would.
  • Check whether member, group, gig, and pay visibility match your intention.
  • Confirm that invite links are going to the right people.
  • Revisit settings after a leadership or roster change.

Privacy is part of the workflow. Review settings before the link is already in someone's inbox, group chat, or social post.