Your organisation's service¶

Every organisation in OS uses the service it has: what its plans hold, with the exceptions and trials set for it. This page explains what that service is, how plans, exceptions, trials and demos work, and how the service relates to roles and rules. It has no steps; Plans and exceptions shows how to look at and set up an organisation's service.

The service is a ceiling¶

What someone may do in an organisation comes from roles, groups and rules (Roles and access). The organisation's service sits above them as a ceiling: a rule allows something only inside the service. A rule about something the service does not hold allows nothing; a rule naming more actions than the service holds allows only the actions in the service.

The service only takes away. It gives nobody anything a rule does not allow: a service holding assistants means roles and rules can allow their use, not that everyone gets them automatically. A refusing rule (forbid) always still applies.

OS shows buttons and menus inside the service (What you see in OS): what is not in the service you do not see, even when a role would allow it. The AI features follow the service too: what it does not hold, nobody can use there.

Plans¶

A plan is a named list of items of the service. Each item is a kind of thing, with the actions the plan allows on it: for example "see and use agents", or "knowledge collections", which then covers every action.

Artific puts the plans together and maintains them. An organisation can have more than one plan; its service is then everything those plans hold together. When Artific changes a plan, the change applies to every organisation that has it.

An organisation without a plan has the same service as the organisation above it. As soon as it has one plan, only what its plans and exceptions give counts.

Assistants and chatting with a model¶

An assistant is an agent your organisation has set up. Nobody in OS chats with a bare model: a turn that names no assistant is refused to every person, whatever the service and the rules say, also when they call the AI features directly with their own sign-in. Assistants, calling a tool directly and searching knowledge keep working, as far as the service holds them. There is no plan item for direct chat.

Always in the service¶

A few things are in every service and in no plan, so that no change to a plan can lock an organisation out of its own administration:

• managing its own people: members, invitations and groups;
• roles, attributes and the rules document;
• reading its audit trail;
• reading its own service;
• its webhooks and its feed of events, so an integration you built does not stop when a plan changes;
• its Slack channels, once Slack is switched on in your environment.

What that administration allows is still decided by roles: in an organisation without a single plan, a people-admin invites people as usual.

Your company's sign-in (proving an e-mail domain and linking your company's sign-in service) is not in the service automatically. It is an item like any other, given by a plan or an exception.

Exceptions¶

An exception adds one item to one organisation's service, or takes one away, on top of what its plans give. That way one customer gets something extra without a plan being needed for it, or you leave out one item of a plan for them. An exception that takes something away wins over the plans.

An exception can carry a reason: a note for those who manage the service, for example why a customer got something extra. Only those who may change the service see the reason. The organisation's audit trail records the exception, not the reason.

Trials¶

A trial is a plan or an added exception with an end date. A plan can also have a start date, so that its items apply only later. Such a plan does count as one of the organisation's plans at once: from then on, only what its plans and exceptions give counts. On the start date its items come into force, and the AI features follow within a few minutes.

A trial ends by itself. Once its end date has passed, it no longer counts at the next decision: nobody has to do anything. A lapsed plan does stay with the organisation, so its service shrinks to what its other plans and exceptions give rather than falling back to that of the organisation above it. Only when you remove its last plan does the organisation have the service of the organisation above it again. The AI features follow within a few minutes. The organisation's audit trail records the end, with system as who did it.

Demos¶

A demo is an ordinary organisation with a demo plan and an end date on the organisation itself. It lives in the same environment as every other organisation.

• On the end date the demo organisation is suspended: nobody can work in it any more, and the same holds for the organisations below it.
• Thirty days later it is erased, with everything in it.
• If the customer wants to continue, whoever may change the service from the organisation above (Artific, or the partner's administrator) converts the demo into an ordinary organisation: the end date is removed and it gets an ordinary plan. It is then not suspended or erased. If it was already suspended, the organisation above it resumes it afterwards; a demo resumed while its end date is still on it is suspended again.
• When the demo organisation has organisations below it that still exist, it is not erased by itself, until the organisation above it decides.

Partners pass on only what they have¶

An organisation's service always lies inside that of the organisation above it. A partner can therefore never give its customers more than it has itself, and a customer never more to its own departments. When a partner's service shrinks, its customers' services shrink with it.

An organisation's service is set in the organisation above it: by Artific, or by an administrator of the partner who holds org-admin there with reach descendants (Partners). A partner chooses from Artific's plans and sets exceptions and trials; it makes no plans of its own. An organisation does not change its own service. Its administrators do read it: which plans and items it holds and when they start and end, not who set them and not an exception's reason.

A plan or exception is removed only by someone acting from the organisation that set it, or one above it. When Artific set a restriction on a partner's customer, the partner cannot remove it.

Roles inside the service¶

Whoever gives a role, has a group give roles or writes a rule can grant only what lies inside the organisation's service. When a custom role, a group or a rule reaches beyond it, OS refuses the grant with the message This is not part of your organisation's service, even before checking whether you hold what you give away (Nobody grants more than they hold).

You can always give the built-in roles: they are the same in every organisation and the service only makes them smaller. When the service shrinks later, custom roles and the rules document keep their rules; only what they allow becomes less. When the service grows again, everything applies again.

Every change to an organisation's service goes into its audit trail: who changed what, from which organisation, and the plan or item before and after.