directus_users they will show up on the user page/form by default.@benhaynes I am sorry, but I am unable to find the page where I can add additional fields. Could you please explain where such functionality is located? Sorry again, but I really can't find it. (I have the latest version of Directus)
Ahh, the App doesn't show the Collections in the App, but you can add them manually in the database for now and it should work. Here is a ticket you can follow for when this will be possible within the App GUI:
Hi. @benhaynes
I understand that you explained how to customize fields in directus_users table, but I want to add a M2O field from another self-created collection (not directus_ table). How to do it?
Just follow the normal M2O flow in field setup... no difference then.
https://docs.directus.io/guides/relationships.html#many-to-one
@benhaynes
😳 I'm sorry I asked the wrong question before. I'm going to clarify how to do it with this diagram. I want to add an "area" field (from another collection) to "directus_user"
illustration:

Ahh, reversed! This would be a manually set up M2O on the Directus users table. We'll be making this available in the app soon, but for now you can set this up manually in the database.
Excuse me, how do you make manual adjustment from a database?
I must do this:
ALTER TABLE directus_user ADD FOREIGN KEY (area_id) REFERENCES area(id);
Is correct, Automatically insert M2O on UI?
No, it's done through new records within directus_fields and directus_relations. we don't have official documentation for that since it's not officially supported. But you can look at how other many to one relationships are set up in the system tables to understand how it works.
Even though the Admin UI doesn't show it, we can force navigate to it by hacking the URL to admin/#/settings/collections/directus_users and from there we are able to add fields to users. Some quirks: 1) not able to order the fields ;) 2) must do a full page reload.
What's even more interesting: We can "unhide" the token field, and we can set the token directly from the UI when needed for API access, instead of going to the database.
That sounds about right @rdsubhas — it's nearly possible/supported, but we haven't spent the time to formally get it working since we want to focus on stability/bugs first.
This is one of those "nice quirks" we can live with for as long :) The workaround pretty much works for us. Thanks a lot @benhaynes :)
Most helpful comment
This is one of those "nice quirks" we can live with for as long :) The workaround pretty much works for us. Thanks a lot @benhaynes :)