Add a way to hide or restrict access to fields when creating the first user

[joas8211]

I'm developing a multi-tenancy plugin for Payload CMS and I'd like to hide the tenant field from the setup form. Read more about the issue here: joas8211/payload-tenancy#1

Currently the form for creating the first user renders all fields in the collection + couble of hardcoded fields. It doesn't check field access, probably because it would fail anyway in most cases.

I can think of a few of possible solutions for this:

1. Add a field.admin.setup boolean flag for the field to indicate if it's wanted to be shown at setup.
2. Make field.admin.hidden flag a function for conditional rendering.
3. Improve default field access rights and check them at setup form and in the API endpoint it's using.

[DanRibbens]

My first thought is that you could use conditional logic on the field.

// field
admin: {
  condition: () => !window?.location?.includes('/create-first-user'),
}

I haven't tested this yet, so you might need to play with it to get it to work. I would also name the function and assign it where you need for readability and reuse.

Does that solve your issue?

[joas8211]

I tried it, and it didn't work. The conditional logic doesn't seem to run on that form either.

[pcbal]

Create first user > upload avatar> does that field work before any user is present? When clicked on the upload link a white screen of death is all that is currently available.

[choutkamartin]

What @DanRibbens wrote works. However you need to check if window is available or not. Here's my snippet:

For my use case the first user page is located at /admin/create-first-user.

{
  name: "image",
  type: "upload",
  relationTo: "media",
  admin: {
    condition: () => {
      if (typeof window !== "undefined") {
        const path = window.location.pathname;
        if (path === "/admin/create-first-user") {
          return false;
        }
        return true
      }
    },
  },
},

[joas8211]

Conditional rendering worked indeed. I was just being dumb. I somehow managed to mixup the fields and so tried to apply it to a wrong field of a wrong collection. Thanks for helping me @DanRibbens and @choutkamartin!