Skip to content
Anslation

Enterprise browser automation with roles, reviews and run evidence.

AnsBot gives each bot its own team with five roles, keeps every change in a numbered version that can go through review, and lets you mark the steps that must wait for a person. Runs you start can use the test, staging or production environments you define; every run masks values marked secret and keeps a log, its output and screenshots where it stops.

What you control today. Per bot, enforced on the server.

AnsBot controls
ControlWhat it does
Team rolesOwner, staff, developer, operator and reviewer per bot; each member allowed or refused training, running, publishing and managing the team.
VersionsEvery change is a numbered version, draft, published or retired; compare two and roll back.
ReviewsA version under review, or rejected, cannot be published; each decision is kept.
Approval stepsMarked steps stop the run until a person approves or rejects them.
Permission policyAllowed actions and domains per bot, with approval before submit-like clicks, uploads, stored sign-ins and moves to another domain.
EnvironmentsTest, staging and production presets for version, inputs, sign-in, browser, queue and attempts.
Quality gateScores whether a bot is ready; runs started from the console and client portal runs must pass it.
MaskingValues marked secret become [redacted] in logs, outputs, errors and callbacks.
RetriesFailed attempts retry with growing gaps, then wait in a dead-letter queue for an operator.
Callback signingResults posted to your systems carry an HMAC-SHA256 signature when the endpoint has a signing key.

Controls you can switch on, and records of what happened.

  • Review before going liveA bot setting: only versions with an approved review go live, run in production or run from schedules, webhooks and the client portal. Versions published before you switch it on count as reviewed while they stay published.
  • Four-eyes approvalA bot setting: whoever asked for a review, started a run that its environment holds for approval, or staged a repair cannot approve it.
  • No forcing past checksA bot setting: apart from the platform owner's recorded override, nobody can force a run, a review or a publish past a quality or permission check that blocks. Production batches, retries and resumes must pass the quality check; runs from schedules and webhooks skip it.
  • Locked published versionsA bot setting, on whenever reviews are required: AnsBot refuses any edit to a published version's steps; you edit a new draft made from it.
  • Approval before a run startsAn environment setting that holds each run started with it until a person approves; runs from schedules, webhooks, batches and the client portal do not use environments.
  • Audit logPublishes, reviews, runs people start, approvals, repairs, token rotations, portal invites and policy changes, for the bots you can open; filter it and export it as CSV.
  • Data retentionKeep finished runs for a set number of days; once Anslation switches on the scheduled cleanup, it deletes older ones with their logs, outputs and screenshots, unless a retry or an open repair still needs them.
  • Usage overviewRuns, outcomes, run time and waiting approvals per bot, over a recent period.
  • One recorded overrideOnly Anslation's platform owner can override the review, four-eyes and check rules, and every override is written to the audit log.

How work moves through a team. Each role does its part.

  • Developers build

    Record or draft a bot and edit its steps.

  • Reviewers check

    Approve or reject a version before it is published.

  • Publishers ship

    The owner, or a member with the publish right, publishes the version.

  • Operators run

    Start, pause and retry runs, and answer approval requests.

  • Owners manage

    Manage the team and the client billing.

Not available. Said plainly.

In place today

  • Runs on Anslation's servers, in a fresh browser each time.
  • Keeps each bot to its creator, its team and AnsBot administrators.

Not offered

  • Company workspaces: access is set per bot today.
  • Workers in your own network: runs always use Anslation's servers.
  • A choice of where data is kept.
  • Access keys for scripts: outside systems start runs through webhook tokens.

Sign-in and access. One account, per-bot teams.

  • Your Anslation accountYou sign in to AnsBot with your Anslation account, through your company's single sign-on where your company has set it up in Anslation One.
  • Turned on per accountAn administrator gives each person AnsBot access; anyone without it is asked to request it.
  • Who can open a botIts creator, the members of its team and AnsBot administrators.

Enterprise questions, answered.

Still have a question? Ask us

Who can publish a bot?

The bot's owner, and team members given the publish right. Roles per bot are owner, staff, developer, operator and reviewer, and each member can be allowed or refused training, running, publishing and managing the team.

Can a reviewer stop a release?

Yes. Send a version for review and it cannot be published while the review is pending or after it is rejected; every decision stays in the version's review history.

How are sign-in details for websites kept?

In the bot's vault, stored encrypted with an application key and shown only as a masked preview. A run fills them through {{credential_username}} and {{credential_secret}}, and they appear as [redacted] in logs, outputs and callbacks.

Can AnsBot reach systems behind our firewall?

No. Runs reach public websites only, from Anslation's servers, and private and internal addresses are refused; AnsBot's workers cannot be hosted in your own network.

Can we limit what each person can do?

Yes, per bot: add people to a bot's team with a role and allow or refuse each right. Someone outside the team, without AnsBot administrator access, cannot open that bot.

Taking AnsBot to your team? Tell us what you need to check.

Tell us the web task and the site it runs on. We read every request and reply by email.

Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838