Users

User (model)

Internal name:users.User
Implemented by:User

Views on User

  • Users (Users) (Menu Configure ‣ System ‣ Users) – Shows the list of all users on this site.
  • Users (MySettings)
  • Users (UsersOverview)

Fields in User

  • Username (username, CharField) – Required. Must be unique.
  • User Profile (profile, ChoiceListField to User Profiles) – Users with an empty profile field are considered inactive and cannot log in.
  • ... and ID (id, AutoField), Created (created, DateTimeField), Modified (modified, DateTimeField), Password (password, CharField), Initials (initials, CharField), First name (first_name, CharField), Last name (last_name, CharField), e-mail address (email, EmailField), Remarks (remarks, TextField), Language (language, LanguageField), Partner (partner, ForeignKey to Partner)

Actions on User

  • Table (landscape) (as_pdf, PrintTableAction) – Show this table as a pdf document
  • Table (portrait) (as_pdf_p, PortraitPrintTableAction) – Show this table as a pdf document

Tables referring to User

  • My Memberships (MembershipsByUser)
  • Authorities taken (AuthoritiesTaken)
  • My Text Field Templates (MyTextFieldTemplates) (Menu Configure ‣ Office ‣ My Text Field Templates)
  • Authorities given (AuthoritiesGiven)

User Profile (field)

The profile of a user is what defines her or his permissions.

Users with an empty User Profile field are considered inactive and cannot log in.

Authority (model)

Internal name:users.Authority
Implemented by:Authority

Views on Authority

  • Authorities (Authorities) (Menu Explorer ‣ System ‣ Authorities)
  • Authorities given (AuthoritiesGiven)
  • Authorities taken (AuthoritiesTaken)

Fields in Authority

  • User (authorized, ForeignKey to User) – The user who gets authority to act in your name.
  • ... and ID (id, AutoField), Author (user, ForeignKey to User)

Actions on Authority

  • Table (landscape) (as_pdf, PrintTableAction) – Show this table as a pdf document
  • Table (portrait) (as_pdf_p, PortraitPrintTableAction) – Show this table as a pdf document

Team (model)

Internal name:users.Team
Implemented by:Team

A Team is a group of users that work together.

Belonging to a Team or not has no influence on access permissions. These depend on your user profile.

Views on Team

  • Teams (Teams) (Menu Configure ‣ System ‣ Teams)

Fields in Team

Actions on Team

  • Table (landscape) (as_pdf, PrintTableAction) – Show this table as a pdf document
  • Table (portrait) (as_pdf_p, PortraitPrintTableAction) – Show this table as a pdf document

Teams (view)

Internal name:users.Teams (Teams)

For illustration, the demo site has the following teams:

ID Designation Designation (de) Designation (fr)
       

Membership (model)

Internal name:users.Membership
Implemented by:Membership

A membership is when a given User belongs to a given Team.

Views on Membership

  • Memberships (Memberships)
  • My Memberships (MembershipsByUser)

Fields in Membership

  • ID (id, AutoField), Author (user, ForeignKey to User), Team (team, ForeignKey to Team)

Actions on Membership

  • Table (landscape) (as_pdf, PrintTableAction) – Show this table as a pdf document
  • Table (portrait) (as_pdf_p, PortraitPrintTableAction) – Show this table as a pdf document

User Profiles (view)

Internal name:lino.UserProfiles (UserProfiles)

The list of user profiles available on this site.

Each user profile is a set of user levels (one for each functional group), leading to an individual combination of permissions.

The demo database has defined the following user profiles:

value name text User Level (System)
000 anonymous Anonymous  
100 user User User
900 admin Administrator Administrator

Note that we show here only the “general” or “system” userlevel. Open Explorer ‣ System ‣ User Profiles in your Lino to see all application-specific userlevels.

EN DE FR

Table Of Contents

code pypi
user | technical