# Understanding interfaces

Interfaces allow access to the system with preset values for

- Wrapper
- Stylesheet
- Template
- Language
- User context

When accessing the interface the user is redireceted to the main page with the correct parameters set. In case the user context is active, a session with a matching user profile is also created i process.

The following types of record operations are allowed

- Create new records
- Update an existing record

### <span class="mw-headline" id="bkmrk-create-operations-1">Create operations</span>

Create operations require no additional security information and can be used directly.

URL for testing the interface:

http://\[server name\]/\[application\]/webinterface?\[interfacename\]

### <span class="mw-headline" id="bkmrk-update-operations-1">Update operations</span>

When updating an existing record a security token must be passed along to the interface:

- The right data is displayed for the user
- Bind user session to this piece of data

A security token contains

- a reference to the record
- a timestamp when the token was issued
- a signature that guarantees that the server issued the token

URL for testing the interface: http://\[server name\]/\[application\]/webinterface?\[interfacename\]=\[security token\]

Security tokens can be generated in various ways

- Create a status action that generates a notification
- Administrator tool: Designer &gt; Modules &gt; Admin Services &gt; BuildSecuityToken
- Add the special "Token display" field to a solution

### <span class="mw-headline" id="bkmrk-questionnaires-and-e-1">Questionnaires and email invitations</span>

Generation of security tokens are closely tied to the use of questionnaires and status actions.

The guide [Questionnaires](https://docs.tsnocode.com/books/entities/chapter/questionnaires "Tutorial/Questionaires") covers such an example.