# A read-only seat asks and performs no act

Source: https://docs.tightly.io/help/ask/read-only-seat
Reviewed: 2026-09-07

## The sentence

When a viewer asks Ask Tightly to fire a skill, the skill is not started and Ask Tightly relays the refusal it was given:

> Firing a skill takes the same permission as running it from the Skills page (read-write); this seat is read-only.

When a press from a viewer's seat reaches a page's write, the route answers with the sentence every role check in Tightly shares:

> Your access level does not cover this. Ask an admin on Team to raise it.

A few routes answer a role check with a sentence of their own that names the act; the meaning is the same.

## What it means

Your organisation has three roles, set on [Team](../settings/team): Admin runs the workspace, Member works the product, Viewer sees everything and touches nothing. A viewer reads every page and asks Ask Tightly anything: starting a conversation, sending a question and reading an answer all take only a viewer's seat. What a viewer cannot do is write, and Ask Tightly does not carry a write around that.

Ask Tightly offers a viewer no act to press. Every act it can propose needs a seat that may write, so for a viewer the suggestion stands as a plain sentence rather than a button. The one exception is the dry run of a commitment's compile on Tightly Pro, which writes nothing. Keeping an answer on the Board or on Home is a write too, so a viewer is not offered it, and renaming or deleting a conversation needs a Member's seat. Every act Ask Tightly performs runs under your own seat, so the same door has the same lock whether you press it or ask for it.

Firing a skill is the plainest case: the run would write as the skill's author, so the fire takes the permission the Skills page takes, and a read-only seat is told so in words rather than handed a run it could not have started itself. On Tightly Lite Ask Tightly cannot fire a skill at all, so a Lite seat never meets that first sentence; the second one is the refusal a read-only seat can meet on any plan.

It is not a plan gate, which names what sells the room. It is not a failed read: the page read, and refused the write. And it is not a fault of the page: a button a viewer can see is still a button the route refuses.

## What to do next

Ask an admin at your organisation to change your role on Team; Member is the role that works the product, and Admin adds the team, the settings and every door. Until then, read, ask and share what Ask Tightly answers; none of that is a write. Where your plan carries Skills and one needs firing now, a Member or an Admin fires it from the Skills page.

## Who to ask

An admin at your organisation, whose name Team shows. Ask Tightly answers from this article and can say which role an act needs, but the grant is your organisation's own.