Work on the user template pages or link an additional page to user

[davo]

I'm planning out a new project and I intend to have  information stored against each user. Some may be editable by the users and other fields not editable by the users.

Would it be best to simply create the fields in the users' templates but then use a module to restrict viewing and editing

||

Would it be best to create a linked user template to store this additional information where the user just doesn't have access to the template?

The sort of information that might be in the extra restrictive fields are information like scores and points.

[marcus]

Would it be best to simply create the fields in the users' templates but then use a module to restrict viewing and editing

||

Would it be best to create a linked user template to store this additional information where the user just doesn't have access to the template?

The first one, since the second one sounds redundant and users are pages anyway. And you could use roles to control viewing and editing. Detecting a user's role or create new ones via a module is way easier than to manage a somewhat parallel structure.

[LostKobrakai]

I'm currently using a dual approach. Fields like addresses and single information fields are within the user template, while conversations are own pages linked via a pageTable field. It made more sense to store conversations / single messages in a centralized fashion instead of combining them from different user pages.