Manage your resource with Discord

1. Claim the resource

Open your resource page and select Claim as maintainer. Website resources can verify through a DNS TXT record or a signed file at the fixed /.well-known path. GitHub repository resources use the repository proof shown in the claim flow.

The first valid proof wins. After verification, your signed-in Discord identity can edit the resource record; claiming does not create a public endorsement or guarantee.

GG Atlas checks a new proof after about 10 minutes, then again around 30 and 60 minutes while it remains pending. DNS providers can take time to publish changes, so keep the proof in place until the resource page shows maintainer confirmation.

2. Keep the entry current

In the Listing tab of the Maintainer workspace, update the description, functionality, collaboration requests, availability, account-access statement, delivery platforms, release note, logo, screenshots, and optional public Discord invite. Use concise user-facing language and save a release note when a change matters to users.

The public Discord invite is optional. GG Atlas accepts an invite code or a normal Discord invite URL and displays it as a link to your community. It does not grant the bot access or verify ownership.

3. Share the verified resource record

After claiming, the resource workspace provides a copy-paste status card for your website or README. It links to your exact GG Atlas record and shows only the current maintainer-confirmed and reachability facts. It is not an endorsement, safety rating, or uptime guarantee.

The card is a normal linked SVG image with no script to install. It is cached for a short period and refreshes from the public record, so update the resource details before sharing it.

4. Connect GG Atlas Bot

In the resource workspace, select Connect bot. Copy the short setup code, install or re-authorize GG Atlas Bot in your server if needed, then run /setup code:YOUR-CODE.

Choose either a new private gg-atlas-your-resource channel or an existing channel such as gg-atlas-feedback. Setup confirms that the bot can post before it saves the connection. If Discord reports a permission issue, grant the requested channel permissions and repeat setup with a fresh code.

5. Handle user feedback

Users can submit general feedback, bug reports, offline reports, and feature requests from the resource page. GG Atlas Bot posts each item to the configured channel. A maintainer can acknowledge it, resolve and close it, or mark it not reproducible in Discord or from the resource workspace.

The resource workspace keeps open and closed feedback available even when Discord is disconnected. Discord controls are a convenience, not the source of record.

6. Open a collaboration request

The Collaboration toggles in the Listing tab can advertise a need for contributors, a new maintainer, testers, translators, or integrations. Save them with your other resource changes. Each request expires after 30 days unless renewed.

Add a public Discord invite when you want people to respond. The public request opens that invite directly. GG Atlas does not create channels or threads for collaboration, and private bot feedback channels are never promoted as public discussions.

7. Automate version details when useful

Website resources can publish the optional JSON file described in theautomatic listing updates guide. GG Atlas reads it during normal monitoring and records supported version and scope as a maintainer statement. It never changes availability.