The issue is likely related to the ​*key*​ vs ​*display name*​ distinction for resources. When creating a resource, there are two separate fields: (1) (2) • ​*Key*​ – A URL-friendly identifier (slug) that must be unique within the environment. You query resources using this key. • ​*Name*​ – The display name shown in the UI. The key must be unique, while the name can be more flexible. (3) ​*What's likely happening:*​\ If you created

client

as the key, Permit may be automatically generating

clients

as a variant or the keys are conflicting due to similar naming. Check the ​*key*​ field of your existing

client

resource—it might already be

clients

or vice versa. ​*Solution:*​\ Use distinct keys for each resource. For example: • Resource 1: Key =

client

, Name = "Client" • Resource 2: Key =

clients_resource

(or another unique key) , Name = "Clients" You can verify and manage resource keys via the API or UI by chec

To learn more, see the sources I considered: [[1] Create](https://docs.permit.io/sdk/golang/resource/Create) [[2] createResource](https://docs.permit.io/sdk/nodejs/resource/create-resource) [[3] Migrating v1 to v2](https://docs.permit.io/api/v2-migration-guide)

Thanks for tagging me @Or Weis. I'll look through relevant sources and get back to you shortly.

The previous response covered the key distinction well. To add more detail: When you create a resource, you define both a ​*key*​ (the unique, URL-friendly identifier/slug) and a ​*name*​ (the display name) . (1) (2) The key must be unique within the environment. Permit may be preventing you from creating

clients

because: • Your existing

client

resource might already have

clients

as its key • Or the system is detecting a collision based on key similarity ​*Workaround:*​ 1. Check your existing

client

resource's ​*key*​ in the Policy Editor (not just the display name) 2. Use a distinctly different key for your new resource, such as: • Key:

clients_list

or

all_clients

, Name: "Clients" • Key:

client_single

, Name: "Client" (if you want to rename the existing one) You can update an existing resource's name and other properties (though not the key itself) using the SDK:

resourceUpdate := models.NewResourceUpdate()
resourceUpdate.SetName("New Name")
resourceUpdate.SetDescription("New Description")

(1)

const response = await permit.api.updateResource(
  resourceId,
  JSON.stringify(resource)
) ;

(2) If you're still hitting issues after verifying the keys are different, this may be unexpected behavior worth investigating. In that case, could you share: 1. Which Workspace / Project / Environment you're using 2. The exact key and name of your existing

client

resource 3. The exact key and name y

To learn more, see the sources I considered: [[1] Update](https://docs.permit.io/sdk/golang/resource/Update) [[2] updateResource](https://docs.permit.io/sdk/nodejs/resource/update-resource)

aarete.com default project (the only one) environment = dev

Anything else you need to check this out?

It works on my env, can I have your permission to log in to your workspace and try it myself there?

I’m having the same problem adding the admin resource in my UAT environment and this one is a blocker.

image.png