Hello I am confused by the notion of system types: I understand, that the User type is a system type in legacy projects for the integrations to work (https://www.graph.cool/docs/reference/database/data-modelling-eiroozae8u#system-artifacts-(only-for-legacy-console-projects). But when I try to rename the user type after upgrading the project to a graphcool service it still won’t let me do it: “You tried renaming a system model. This is not possible. modelName: User”. Did I miss sth. or are system types not only relevant in legacy projects?

You can create a new

type

with the same fields as

User

type, but cannot remove

User

type from schema.

Ok, thanks. That is actually what I am doing now. But still I find it weird, that User still seems to be a system type, despite the fact that there are no integrations possible anymore and authentication works with every node…

I would say it’s more of a backward compatibility issue, but not for certain.

So you suggest that “upgrading” a project to the new graphcool service structure does not strip the system type restrictions on the User type, despite newly created projects do not have this restriction? That would be a bug in “upgrading” wouldn’t it? In any way thanks for your help! At that point I guess only @nilan could shed more light on this issue.