# UserSettings: Twinfield User settings ## Documentation Settings of one user. The nested blocks the answer also holds - the offices the user may see, the time and expenses settings and the SMS logon services - are not exposed, with the exception of the single-valued elements of each. - Catalog: `Twinfield` - Schema: `Settings` - Primary Keys: `code` - Label: User settings The data in this table is partitioned per value of the `COMPANY_CODE` column. This is a read-only table function. The Twinfield API may not support changing the data or the Invantive UniversalSQL driver for Twinfield does not cover it. In the latter case, please use the table NativePlatformScalarRequests to upload data to the Twinfield API. ## Parameters of Table Function The following parameters can be used to control the behaviour of the table function `UserSettings`. A value must be provided at all times for required parameters, but optional parameters in general do not need to have a value and the execution will default to a pre-defined behaviour. Values can be specified by position and by name. In both cases, all parameters not specified will be evaluated using their default values. Value specification by position is done by listing all values from the first to the last needed value. For example: a `select * from table(value1, value2, value3)` on a table with four parameters will use the default value for the fourth parameter and the specified values for the first three. Value specification by name is done by listing all values that require a value. For example with `select * from table(name1 => value1, name3 => value3)` on the same table will use the default values for the second and fourth parameters and the specified values for the first and third. | Name | Data Type | Required | Default Value | Documentation | |---|:---:|:---:|:---:|---| | `code` | `` | ☐ | | Code of the user to read. | | `COMPANY_CODE` | `` | ☐ | | Code of company. | ## Columns of Table Function The columns of the table function `UserSettings` are shown below. Each column has an SQL data type. | Name | Data Type | Label | Required | Documentation | |---|:---:|---|:---:|---| | `ACCEPTEXTRACOST` | `char` | Accept extra cost | ☐ | Whether extra costs are accepted when the role of the user changes. | | `ACCOUNT_FAILEDLOGONS` | `int32` | Failed logons | ☐ | | | `ACCOUNT_LASTLOGON` | `datetime` | Last logon | ☐ | Moment the user logged on last, in the time zone of the platform. | | `ACCOUNT_SSO` | `varchar2` | Single sign-on | ☐ | | | `CODE` | `varchar2` | Code | ☑ | Code of the user. | | `COMPANY_CODE` | `varchar2` | Company ID | ☑ | | | `COMPANY_NAME` | `varchar2` | Company Name | ☑ | | | `CREATED` | `datetime` | Created | ☐ | | | `CULTURE_NAME` | `varchar2` | Culture name | ☐ | | | `CULTURE_NATIVENAME` | `varchar2` | Culture native name | ☐ | | | `CULTURE` | `varchar2` | Culture | ☐ | The culture Twinfield is shown in, such as nl-NL or en-GB. | | `DEMO` | `char` | Demo | ☐ | Whether the user serves training purposes only. | | `EMAIL` | `varchar2` | Email | ☐ | | | `EXCHANGEQUOTA` | `int32` | Exchange quota | ☐ | Twinfield Analysis quota. | | `FILEMANAGERQUOTA` | `int32` | File manager quota | ☐ | | | `INVITATIONSTATUS` | `varchar2` | Invitation status | ☐ | One of NotInvited, Invited or Active, on the Wolters Kluwer account of the user. | | `ISCURRENTUSER` | `char` | Is current user | ☐ | Whether this is the user the connection logged on with. | | `LEVEL` | `varchar2` | Level | ☐ | | | `MODIFIED` | `datetime` | Modified | ☐ | | | `NAME` | `varchar2` | Name | ☐ | | | `NAMEVIEW` | `varchar2` | Name view | ☐ | | | `OFFICE_DEFAULT_NAME` | `varchar2` | Default office name | ☐ | | | `OFFICE_DEFAULT` | `varchar2` | Default office | ☐ | Company the user starts in. | | `OFFICE_RESTRICTED` | `char` | Office restricted | ☐ | Whether the user is restricted to the companies listed, rather than seeing every company of the organisation. | | `ROLE_LEVEL` | `varchar2` | Role level | ☐ | | | `ROLE_NAME` | `varchar2` | Role name | ☐ | | | `ROLE_SHORTNAME` | `varchar2` | Role short name | ☐ | | | `ROLE` | `varchar2` | Role | ☐ | Code of the role the user is linked to. | | `SHORTNAME` | `varchar2` | Short Name | ☐ | | | `SMSLOGIN_PHONENUMBER` | `varchar2` | SMS logon phone number | ☐ | Number the SMS is sent to when the SMS logon package is enabled. | | `STATUS` | `varchar2` | Status | ☐ | One of active, deleted or hide. A user used in a transaction becomes hidden rather than deleted. | | `SUPPORT_COUNT` | `int32` | Support count | ☐ | | | `SUPPORT` | `varchar2` | Support | ☐ | | | `TOUCHED` | `int32` | Touched | ☐ | Count of the number of times the settings were changed. | | `TYPE` | `varchar2` | Type | ☐ | One of accountant, accountantcustomer or regular. |