Identity and sign-in
Session controls
Autessa admins choose how long members stay signed in without activity, from 15 minutes to 30 days, cap how long a CLI sign-in may last, from 1 to 720 hours, and decide whether Drive can be used from computers. Sign-in is also tied to the network it started on, so moving from Wi-Fi to a phone connection asks members to sign in again.
The problem
What problem does it solve?
An unattended laptop that stays signed in for a month is a risk; a session that times out every few minutes is a tax on everyone. Each company needs to set its own balance, including for the command line and desktop file access.
How it works
- 1
Open Company Settings
From Company → Team, click Company Settings.
- 2
Set Sign out after inactivity
Pick a length from 15 minutes to 30 days, or Default (1 hour). Any activity starts the clock again. It applies to everyone, including people already signed in.
- 3
Cap CLI sign-ins
Set Maximum CLI sign-in length. A member who asks for a longer session with autessa login --session-hours is capped to it.
- 4
Decide on Drive from computers
Allow or block connecting Drive as a network drive, and Drive in the Autessa desktop app. Turning one off disconnects members right away; their files stay in Autessa.
Every option
Session controls: settings and options
| Setting | What it does |
|---|---|
| Sign out after inactivity | 15 minutes to 30 days, or Default (1 hour). Covers team-only apps built in the App Builder too. |
| Maximum CLI sign-in length | 1 to 720 hours. Applies to new CLI sign-ins. |
| Allow connecting Drive as a network drive | Members add Drive in Finder or File Explorer with an app password. |
| Allow Drive in the Autessa desktop app | Turning it off removes Drive from members’ computers. |
| App passwords | Each member creates and names their own, such as “Work laptop”, and removes them at any time. Removing one disconnects that computer right away. |
| Network-bound sign-in | Always on: switching networks asks for sign-in again. |
Permissions
Who can do what?
| Who | What they can do |
|---|---|
| Members with Manage Team Members | Change every company setting on this page. |
| Every member | Create and remove their own app passwords. |
| Members of several companies | Follow the settings of the company they are working in. |
What to know
- Longer lengths are convenient on trusted devices but leave an unattended computer signed in for longer.
- Apps you publish to outside visitors have their own sign-in length per app.
Connections
How Session controls connects to the rest of Autessa
Reports, policies and security questionnaires are on the Autessa Trust Center.
FAQ
Session controls: questions
How long do Autessa sessions last?
By default, members are signed out after 1 hour without activity. Admins can choose anything from 15 minutes to 30 days for the whole company.
Can I limit how long the CLI stays signed in?
Yes. Maximum CLI sign-in length caps every new CLI sign-in at 1 to 720 hours, even if someone asks for longer.
Can I stop people mounting Drive on their computers?
Yes. Two company switches control Drive as a network drive and Drive in the desktop app, and turning either off disconnects members right away.
Get started with Session controls
Admins set one sign-out-after-inactivity length for the company, cap how long CLI sign-ins last, and decide whether Drive can be used from computers, while sign-in stays tied to the network it began on.
Reports, policies and questionnaires live on the Autessa Trust Center.
100% customizable, code and all
Make Autessa Security & Compliance fully your own.
Use it out of the box, then change anything. Ask Autobot, Autessa’s AI builder, for a new field, screen, report, workflow or agent and it builds it into your copy of the app. Or open the code and edit it yourself. Nothing is locked: the app, its data and its code are yours.
Start free and make it yours