Asset Groups

Define which of your connected accounts a set of users is allowed to see.

Overview

An asset group is a named set of the accounts you have connected to Seemore — Snowflake accounts, and the dbt, orchestration, and BI tools alongside them. Granting an asset group to a team (or directly to a user) is what makes the data behind those accounts visible; anything outside the group stays out of reach across the whole product.

Asset groups are the only mechanism that restricts what a non-Owner can see. Domains, by contrast, only filter what is already visible.

Required role to configure: Owner.

Admins and below can see asset groups and select them when configuring a team, but only an Owner can create, edit, or delete them.

Each asset group shows its estimated annual cost, the accounts it covers, and who it is granted to.

---

What the Columns Mean

Column	What it shows
Asset group name	The group's name, as it appears when you attach it to a team or user.
Est. Annual cost	The projected annual spend of the accounts in the group — a quick sense of its scope.
Assets	The accounts the group currently resolves to.
Teams	The teams this group is granted to.
Users	Users the group is granted to directly, without going through a team.
Owner	The user who created the group.

---

How to Create an Asset Group

1. Go to Settings → Access control → Asset groups.

2. Click Create and choose Asset Group.

3. Fill in:

   • Asset group name — required.

   • Description — optional.

   • Account — pick the accounts to include explicitly, or

   • Object tags — pick tag values, and every account carrying one of them is included.

4. Click Create Asset Group.

Choose the accounts explicitly, or select object tags and let matching accounts be included automatically.

---

Choosing Accounts vs. Object Tags

The two selectors are alternatives — you may use either, or both, and the group resolves to everything that matches.

Pick accounts explicitly when the set is small and stable: "the production warehouse and the Tableau workspace it feeds."

Use object tags when you want the group to stay current on its own. A group defined as environment = production picks up any newly connected account tagged that way, with no edit to the group. See Tags Management for how to apply object tags.

Tag-based groups are evaluated on every request, so tagging a new account grants access to it immediately — and removing the tag takes it away just as fast. Review tag-based groups whenever you change your tagging scheme.

---

How to Edit or Delete an Asset Group

Hover a group's row and use the actions on the right:

• Edit asset group — change the name, description, accounts, or object tags. Access follows the change on the members' next request.

• Delete asset group — remove it after a confirmation. Every team and user it was granted to loses that access, so check the Teams and Users columns first.

---

Notes & Best Practices

• Group by trust boundary, not by convenience — production versus non-production, or one group per business unit, tends to age well.

• Name groups after what they contain, since the name is all an Admin sees when attaching a group to a team.

• Grant through teams, not directly to users, so access stays legible in one place.

• Remember the single-account fallback. In a workspace with exactly one Snowflake account connected, a user with no grants at all still sees that account — asset groups start restricting once there is more than one account or the user has any grant. See Access Control.

• Owners bypass asset groups entirely. If someone must not see an account, they cannot be an Owner.