in multi-tenancy, getting wrong response message...

[red valve]

Hi community, I have been trying to implement multi-tenancy in my project. I have a collection, with slug work defined here:

import { CollectionConfig } from "payload/types";
import { tenants } from "../../access/tenants";
import { tenant } from "../../fields/tenant";
import { isTenantAdmins } from "../../access/isTenantAdmins";

const Work: CollectionConfig = {
  slug: "work",
  access: {
    create: tenants,
    read: tenants,
    update: tenants,
    delete: isTenantAdmins,
  },
  fields: [
    {
      name: "id",
      label: "Key",
      type: "text",
      required: true,
    },
    {
      name: "value",
      type: "textarea",
      required: true,
    },
    tenant,
  ],
};

export default Work;

When-ever I am trying to create a data in work collection via postman. I am getting response message as tenant created successfully instead of work created successfully. Why is this happening and how to resolve this issue.

[shrewd fox]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Lexical Rich Text
• Drafts
• Uploads
• Uploads
• Uploads

[marble basalt]

I believe this is actually a bug. I meant to raise this earlier. For some reason since adding Multitenancy to an application, everytime you add an item to a collection the result is always "tenant" created.

@severe tide Wanted to make you aware. I'll raise a GitHub issue but this has been a thing for a few months now. I imagine other multi-tenant users face the same issue

[jolly patrol]

Hey @marble basalt

Is there an issue created for this ?
where can I look up?

Just wanted to look into it

[marble basalt]

Hi @jolly patrol - Been snowed under with work so haven't had any time to replicate and open an issue. I intend to do this some point this weekend