What is a Guild in OfficeGuilds, and when should you join one?

A familiar group across different games

You and a colleague have played a few lunchtime games. Now two more people want to join in, and someone suggests a name for the group. This is where a Guild becomes relevant: OfficeGuilds describes it as a group for games and invitations, with its own leaderboard.

You can create a Guild or join one by invitation. The About page includes joining a Guild among the reasons to create an account. For an office crowd, that might mean the colleagues who enjoy a word puzzle on Wednesday or a board game when their breaks overlap. A Guild gives that familiar group an identity within the platform.

Choose Guest play, an account or a Guild

Start with what you want to do. A Guild is not a prerequisite for a first game, and an account’s personal features serve a different purpose from a group identity.

• “I want to try one game with a colleague.” Use Guest play: invite a friend by link without creating an account or downloading anything. Guest games do not change experience points, known as XP, or ratings.

• “I want my own profile and progress across games.” Look at the account features. Your nickname and Character card stay with you across games. Signing in lets you challenge a player or use Quick Match to find an opponent. According to the feature overview, rated matches against real players also earn XP and levels.

• “The same people keep returning and want a named group.” Consider creating or joining a Guild. You can share that identity even if each person prefers different games.

• “We want to run a competition with a precise scoring system.” Verify how the available tools work before choosing a format. The public Guild description alone does not explain enough to plan such an event.

These needs can overlap. Someone may want to join a group without competing every time, while another colleague prefers an occasional Guest match. Explain why your group wants a Guild and let each person decide.

What the published Guild features confirm

The official overview confirms that you can create a Guild or join by invitation, describes a Guild as having its own leaderboard, and says the owner chooses whether the Guild profile is public.

It does not explain the Guild scoring formula or every membership setting. Nor does it describe a Guild chat, calendar or tournament organiser. Those omissions do not establish whether a feature exists; they mean you should verify it before relying on it. For arranging times and opponents, your existing work chat is a ready alternative.

What to check before creating or joining

Use this checklist before inviting colleagues. It covers decisions and checks; button names and the exact account flow may change:

1. Confirm the group. Agree who is interested and check whether one of them has already created the intended Guild. This avoids several colleagues setting up competing versions of the same group.

2. Agree the presentation. Choose a name and agree on any images you plan to use in the available profile fields. Avoid internal project names, client details or company branding you are not authorised to publish.

3. Identify the owner. The published features assign the public-profile decision to the owner. Make sure that person knows what visibility the group expects before invitations go out.

4. Review the available settings. Inspect the current account options. If a membership limit, role, permission or ability to transfer ownership matters to your plan, look for an explicit explanation. If you cannot find one, do not build your plan around that capability.

5. Invite deliberately. Use the invitation method the account offers. Tell the intended colleagues the Guild name and why it exists through your usual communication channel.

6. Check the result. Confirm that invitees joined the intended group. Then arrange a specific game separately, including the opponent and the time.

If an invitation fails, first compare the Guild name and the account being used. Ask the inviter to check the invitation in the current interface and follow any displayed error or recovery instructions. Do not assume an old invitation still works or create duplicate Guilds as a first fix. You can arrange a separate Guest game while resolving membership.

Understand visibility before adding identifying details

The owner’s choice about a public Guild profile deserves a specific conversation. The Privacy Policy says public player and Guild pages and leaderboards display profile and game information, such as Character identity, Guild presentation and statistics. Account credentials and private security information are not public profile fields. Read that explanation alongside the available account settings; a preference expressed in work chat does not change those settings.

For an office group, a neutral name and artwork can be a simpler starting point than a department label or a team photograph. Ask before using a colleague’s image or name in group presentation. Do not place client information, internal links or confidential project details in profile text. Review the resulting profile after setup so you know what it actually shows.

The Guild’s visibility and an individual player’s profile are separate things to check. An unpublished Guild profile should not be treated as a promise that every member’s player information is hidden. Check what is shown on each relevant page. If a privacy requirement is essential and the policy or settings do not answer it, clarify it before adding the information.

Read leaderboards without inventing the scoring rules

The public Guild leaderboard says Guild ratings appear as members earn game ratings. It does not give a full scoring formula or a competition period. Before using it to run an office challenge, establish what contributes to the score, which period it covers and whether the view matches the competition you intend. If those answers are unavailable, do not announce rules that depend on them.

For example, four colleagues could arrange four one-on-one matches, with each person playing twice. That schedule does not establish that the Guild leaderboard counts only those four games, resets that week or awards points as they expect. If they want a result for this small event, agree on its scoring and keep a separate record unless the platform’s documented rules clearly support their format.

If your group only wants a shared name and familiar opponents, you can skip the event scoring. For the social side of running a recurring group, see friendly Guild etiquette; this guide concerns what the platform publicly documents and what to verify before relying on more.

A practical office example

Imagine four colleagues who already play occasionally in pairs. Marta and Sam prefer word games; Iryna and Ben enjoy board games. After a few breaks, they decide they would like a shared group name. One person creates the Guild, and the others join by invitation using the options available in their accounts.

They agree on the name and profile visibility first. They keep arranging times and opponents in their existing work chat, where everyone already sees the messages. Here is an example they could send there:

“We’ve made a Guild for our occasional game breaks. Join if you’d like. For Thursday, reply here if you’re free after lunch and say what you fancy playing.”

This is an example invitation message, not an OfficeGuilds notification. The group can continue arranging separate games in pairs. Guild membership itself should not be treated as a promise that four people can enter the same match: check the selected game’s current options.

Start with the need you already have

For a first shared break, a Guest game is enough. When the same group wants a shared identity, look at Guilds together. Agree on presentation and visibility, verify any feature your plan depends on, and arrange the actual games. Keep participation optional and results separate from anyone’s work performance.