Update hierarchies documentation

[mooreds]

This does the following:

• adds FGA support and hosting as a enterprise feature
• adds the enterprise blurb to the Permify example
• updates the modeling hierarchy document to offer FusionAuth FGA by permify as an alternative

[nathan-contino]

Looking good, a few suggestions to make these changes even more readable.

[nathan-contino]

Two asides in a row at the top of a page is a bit of a red flag to me. Can we move this into the "Fine-Grained Authentication" section below, instead? I think if we do that, we can likely get rid of the enterprise blurb you just put in that spot (also improves the flow, as consecutive asides break the flow a bit), but I'll leave that decision up to you.

[mooreds]

oh man, I really wanted to highlight Permify, but I hear you. Removed.

[nathan-contino]

Doesn't the previous example also centralize the auth model? I think we can get rid of that sentence and instead focus on the 'propagates' selling point here, which (iiuc) is a better way of distinguishing this approach anyway.

[mooreds]

good point, I'll rework.

[nathan-contino]

Suggested change

	In this option, you use [FusionAuth FGA by Permify](/docs/extend/fine-grained-authorization/fusionauth-fga), a standalone authorization server.
	This option demonstrates how you can model the same hierarchy using [fine-grained authorization](/docs/extend/fine-grained-authorization/fusionauth-fga) (FGA) with Permify, a standalone authorization server.

Suggestion: define "FGA" before we use the acronym.

[mooreds]

Happy to define FGA before we use it as an acronym. But the product (Permify supported by FusionAuth) is called "FusionAuth FGA by Permify" and I want to use that name. Will rework.

[nathan-contino]

Suggested change

	[Learn more about FusionAuth FGA by Permify](/docs/extend/fine-grained-authorization/fusionauth-fga).
	For more information, see the [fine-grained authorization documentation](/docs/extend/fine-grained-authorization/fusionauth-fga).

suggestion: make it more obvious that we're linking to another section of the FA docs, and reduce usage of the terms "FusionAuth" and "Permify", which can get a bit tiring to read since they're company names, not words.

[mooreds]

See above about that being the product name :) .

[nathan-contino]

Why add EnterprisePlanBlurb here if we don't use it on the page?

[nathan-contino]

Why not use the existing enterprise blurb?

[mooreds]

Hmmm. It's because you can use Permify without an enterprise plan, it is only the support and hosting that require enterprise.

Maybe I can use the blurb here and include a modified version of the text as well.

[nathan-contino]

Suggested change

	"displayName": "FGA by Permify Hosting And Support",
	"displayName": "fine-grained authorization (FGA) with Permify",

Suggestion: define the acronym before we use it; omit 'hosting and support' since we don't specify that for any other features

[mooreds]

well, those are the only parts of Permify we charge for :) .

[Copilot]

Pull request overview

Updates documentation to position FusionAuth FGA by Permify as an Enterprise-supported/hosted option and surfaces it as an alternative approach in the hierarchy modeling guide.

Changes:

• Added “FusionAuth FGA by Permify Hosting and Support” to the Enterprise features list.
• Added a licensing/support section to the FusionAuth FGA by Permify documentation.
• Expanded the “Modeling Hierarchies” guide with an Enterprise-blurb’d FGA alternative and example schema/SDK usage.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
astro/src/content/json/features.json	Adds an Enterprise feature entry linking to the FusionAuth FGA by Permify docs.
astro/src/content/docs/extend/fine-grained-authorization/fusionauth-fga.mdx	Documents licensing/support expectations for FusionAuth FGA by Permify.
astro/src/content/docs/extend/examples/modeling-hierarchies.mdx	Adds an Enterprise FGA alternative section with schema and permission-check example.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

In features.json, other displayName entries use sentence case with a lowercase “and” (e.g. “Advanced and Gaming…”, “Entity Management and …”). Consider changing “Hosting And Support” to “Hosting and Support” for consistency.