-
Notifications
You must be signed in to change notification settings - Fork 4
Add guide: Migrate your group and update its details #10
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
Draft
shrn-werk
wants to merge
4
commits into
gitbook
Choose a base branch
from
claude/tender-shannon-GJ38S
base: gitbook
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
85 changes: 85 additions & 0 deletions
85
docs/user-guides/circles-groups/migrate-group-and-update-details.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,85 @@ | ||
| --- | ||
| icon: user-gear | ||
| description: >- | ||
| How to migrate your group so you can edit it, and how to fill in the new | ||
| group contract properties as an admin. | ||
| --- | ||
|
|
||
| # Migrate your group and update its details | ||
|
|
||
| New properties have been added to the group contract, and group admins need to fill them in. This guide walks you through making your Circles profile an admin of the group and then updating the new fields in the admin app. | ||
|
|
||
| The process is straightforward: you add your Circles profile as a signer of the group's owner Safe, then use that connection to edit the group in the admin app. | ||
|
|
||
| ### Assumptions | ||
|
|
||
| Before you start, this guide assumes the following: | ||
|
|
||
| * You set up your account using [app.aboutcircles.com](https://app.aboutcircles.com). This means you have a signer and a wallet you can connect to that app to modify your account. | ||
| * Your group is owned by a Safe (multisig) that you control. | ||
| * You have a Circles profile and are willing to use it as an admin of the group. | ||
|
|
||
| ### Which steps apply to you? | ||
|
|
||
| * If you created your group using [app.aboutcircles.com](https://app.aboutcircles.com), start at **Step 1**. | ||
| * If you created your group using [circles.gnosis.io/admin/circles-groups](https://circles.gnosis.io/admin/circles-groups), skip to **Step 6**. | ||
|
|
||
| ## Part 1 — Make your Circles profile an admin of the group | ||
|
|
||
| ### Step 1: Find your group | ||
|
|
||
| Open the Group Checker and locate your group: | ||
|
|
||
| {% embed url="https://aboutcircles.github.io/CirclesTools/groupChecker.html" %} | ||
|
|
||
| ### Step 2: Open the owner Safe | ||
|
|
||
| In the **Owner** column, find the owner Safe of your group and click the wallet symbol next to it to open it in the Safe UI. | ||
|
|
||
| <figure><img src="../../.gitbook/assets/group-checker-owner-safe.png" alt=""><figcaption><p>The Owner column in the Group Checker. Click the wallet symbol to open the owner Safe.</p></figcaption></figure> | ||
|
|
||
| ### Step 3: Connect to the Safe UI | ||
|
|
||
| Connect to the Safe UI using your owner EOA — the wallet that owns the Safe. | ||
|
|
||
| ### Step 4: Find your Circles profile address | ||
|
|
||
| Locate the address of your personal Circles profile (for example, via the Gnosis App). | ||
|
|
||
| <figure><img src="../../.gitbook/assets/circles-profile-wallet-address.png" alt=""><figcaption><p>In the Gnosis App, open the QR code panel and copy your wallet address from the Advanced section.</p></figcaption></figure> | ||
|
|
||
| ### Step 5: Add your Circles address as a signer | ||
|
|
||
| In the Safe UI, go to **Settings → Manage Signers** and add your Circles address as a signer. Then sign the transaction. | ||
|
|
||
| {% hint style="info" %} | ||
| Once the transaction is confirmed, your Circles profile is an authorised admin of the group's owner Safe and you can use it to edit the group. | ||
| {% endhint %} | ||
|
|
||
| ## Part 2 — Update the group details | ||
|
|
||
| ### Step 6: Sign in to the admin app | ||
|
|
||
| Go to [circles.gnosis.io/admin/circles-groups](https://circles.gnosis.io/admin/circles-groups) and sign in using your passkey for the Gnosis App. | ||
|
|
||
| ### Step 7: Open your group | ||
|
|
||
| Open your group and select **Edit Details**. | ||
|
|
||
| ### Step 8: Edit the details | ||
|
|
||
| Fill in the new fields: | ||
|
|
||
| * **Description** — Explain the purpose of the group and the benefits of joining. | ||
| * **Group type** — Set this to **closed**. | ||
| * **Contact details** — Provide a way for prospective members to reach you. | ||
| * **Membership Fee** and **Minimum Rep Score** — Optional. | ||
| * **Additional Criteria** — A brief description of how a user can join the group. | ||
|
|
||
| ### Step 9: Save | ||
|
|
||
| Click **Save** to apply your changes. | ||
|
|
||
| {% hint style="success" %} | ||
| That's it — your group details are now updated. | ||
| {% endhint %} | ||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix heading level structure.
The document jumps from a level-1 heading (line 8) to a level-3 heading here, skipping level 2. Markdown best practice requires headings to increment by only one level at a time for proper document structure, accessibility, and navigation.
📝 Proposed fix
Change the level-3 headings to level-2:
Apply the same change to line 22:
📝 Committable suggestion
🧰 Tools
🪛 markdownlint-cli2 (0.22.1)
[warning] 14-14: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3
(MD001, heading-increment)
🤖 Prompt for AI Agents