Adding clarification to group license assignment (#6413)

## What are you changing in this pull request and why?

See
[this](https://dbt-labs.slack.com/archives/C02N953LRDF/p1730737960044729)
for context

## Checklist
- [ ] I have reviewed the [Content style
guide](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/content-style-guide.md)
so my content adheres to these guidelines.
- [ ] The topic I'm writing about is for specific dbt version(s) and I
have versioned it according to the [version a whole
page](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#adding-a-new-version)
and/or [version a block of
content](https://github.com/dbt-labs/docs.getdbt.com/blob/current/contributing/single-sourcing-content.md#versioning-blocks-of-content)
guidelines.
- [ ] I have added checklist item(s) to this list for anything anything
that needs to happen before this PR is merged, such as "needs technical
review" or "change base branch."
- [ ] The content in this PR requires a dbt release note, so I added one
to the [release notes
page](https://docs.getdbt.com/docs/dbt-versions/dbt-cloud-release-notes).
<!--
PRE-RELEASE VERSION OF dbt (if so, uncomment):
- [ ] Add a note to the prerelease version [Migration
Guide](https://github.com/dbt-labs/docs.getdbt.com/tree/current/website/docs/docs/dbt-versions/core-upgrade)
-->
<!-- 
ADDING OR REMOVING PAGES (if so, uncomment):
- [ ] Add/remove page in `website/sidebars.js`
- [ ] Provide a unique filename for new pages
- [ ] Add an entry for deleted pages in `website/vercel.json`
- [ ] Run link testing locally with `npm run build` to update the links
that point to deleted pages
-->

<!-- vercel-deployment-preview -->
---
🚀 Deployment available! Here are the direct links to the updated files:


-
https://docs-getdbt-com-git-calrification-dbt-labs.vercel.app/docs/cloud/manage-access/about-access
-
https://docs-getdbt-com-git-calrification-dbt-labs.vercel.app/docs/cloud/manage-access/cloud-seats-and-users

<!-- end-vercel-deployment-preview -->

---------

Co-authored-by: Leona B. Campbell <[email protected]>

website/docs/docs/cloud/manage-access/about-access.md

@@ -79,7 +79,7 @@ Refer to [role-based access control](#role-based-access-control) for more inform
 
 ## Grant access
 
-dbt Cloud users have both a license (individually or by group) and permissions (by group only) that determine what actions they can take. Licenses are account-wide, and permissions provide more granular access or restrictions to specific features.
+dbt Cloud users have both a license (assigned to an individual user or by group membership) and permissions (by group membership only) that determine what actions they can take. Licenses are account-wide, and permissions provide more granular access or restrictions to specific features.
 
 ### Licenses
 

website/docs/docs/cloud/manage-access/cloud-seats-and-users.md

@@ -124,9 +124,7 @@ Great work! After completing these steps, your dbt Cloud user count and billing
 
 ## Managing license types
 
-Licenses can be assigned manually, or automatically based on IdP configuration
-(enterprise only). By default, new users in an account will be assigned a
-Developer license.
+Licenses can be assigned to users individually or through group membership. To assign a license via group membership, you can manually add a user to a group during the invitation process or assign them to a group after they’ve enrolled in dbt Cloud. Alternatively, with [SSO configuration](/docs/cloud/manage-access/sso-overview) and [role-based access control](/docs/cloud/manage-access/about-user-access#role-based-access-control-) (Enterprise only), users can be automatically assigned to groups. By default, new users in an account are assigned a Developer license.
 
 ### Manual configuration
 
@@ -142,16 +140,9 @@ change.
 
 <Lightbox src="/img/docs/dbt-cloud/access-control/license-manual.png" width="55%" title="Manually assigning licenses"/>
 
-### Mapped configuration
+### Mapped configuration <Lifecycle status="enterprise"/> 
 
-**Note:** This feature is only available on the Enterprise plan.
-
-If your account is connected to an Identity Provider (IdP) for [Single Sign
-On](/docs/cloud/manage-access/sso-overview), you can automatically map IdP user
-groups to specific license types in dbt Cloud. To configure license mappings,
-navigate to the Account Settings &gt; Team &gt; License Mappings page. From
-here, you can create or edit SSO mappings for both Read-Only and Developer
-license types.
+If your account is connected to an Identity Provider (IdP) for [Single Sign On](/docs/cloud/manage-access/sso-overview), you can automatically map IdP user groups to specific groups in dbt Cloud and assign license types to those groups. To configure license mappings, navigate to the **Account Settings** > **Groups & Licenses** > **License Mappings** page. From here, you can create or edit SSO mappings for both Read-Only and Developer license types.
 
 By default, all new members of a dbt Cloud account will be assigned a Developer
 license. To assign Read-Only licenses to certain groups of users, create a new