Module
Platform
The layer that runs underneath every application rather than inside one: who may sign in and what they may do, the automation that reacts to what happens anywhere, the connectors and pipelines that move data in and out, and the analytics that read the whole estate. Administration lives here too — the split between the two was never legible, and both are the platform rather than the business.
8 groups · 31 sections · 130 screens
Access & Security
Who may sign in, what they may reach, and what they did.
Access
9Who may sign in, which directory vouches for them, what they may reach once they are in, who is signed in at this moment, the duties that must not be combined, administrator authority borrowed for a fixed window, and one person’s identity borrowed for another to debug with.
WorkspaceUsersWho may sign in, which roles they hold, and where they are allowed to work.AdminOpenWorkspaceService AccountsIdentities for software. They hold roles like a person but cannot sign in to the console and are never asked for a second step: a secret, shown once, is exchanged for a short-lived token.OpenWorkspaceRolesWhat a role may reach: modules, locations and warehouses.AdminOpenWorkspaceSingle Sign-OnOne connection per directory — SAML 2.0 and OpenID Connect sign people in; OAuth 2.0, WS-Federation, CAS, LDAP and the rest are described — and the email domains each of them answers for, the directory’s MFA and the roles its groups give.OpenWorkspaceProvisioning (SCIM)Your directory creates, changes and deactivates people here through SCIM 2.0, with a token made on this screen and shown once. Groups it pushes give the roles you choose.OpenWorkspaceWeb & User SessionsEvery web session and every signed-in person, with what each is doing now. Sign out one, several, a person, or everybody else.OpenWorkspaceSegregation of DutiesPairs of duties that should not sit with one person, and who currently holds both. Administrators are exempt — they hold every grant by definition.AdminOpenWorkspaceElevated AccessAdministrator authority borrowed for a fixed window, against a written reason, a ticket and two approvals. It ends on its own.OpenWorkspaceAssumed IdentitySigning in as another person to reproduce their transaction, for a fixed window, against a written reason, a ticket and two approvals. Read-only unless it was approved otherwise, an administrator can never be the subject, and every call made with it is recorded and readable afterwards.Open
WorkspaceAudit LogWhat was done, by whom, and to which record.OpenWorkspaceAudit PolicyWhat is recorded. Some entities are mandatory and cannot be switched off.AdminOpenWorkspaceBenchmarksHow the platform is performing against its own targets.OpenWorkspaceSystem & DatabaseThe server this company runs on, its database — connections, locks, settings, and every table with its columns, indexes and a masked preview — and the application’s own source code. Read-only: nothing on this screen can change anything, and every page opened here is recorded in the audit log.AdminOpen
AI Governance
4Switch AI and automated decision tools off, to suggest-only or on, per area; review what they produced about people; see every use; and disclose each tool.
ViewAI SettingsAI features are allowed by default for this company; an administrator can turn any area off. Per area, whether AI and automated decision tools may act here: off (they do not run, and ASK and agents cannot read or change these records), suggest (they may propose, a person decides — every AI output about a person opens a review, and an agent's change waits for approval) or allowed (as the product behaves today). Enforced where each tool runs, not on a screen. Company data is not used to train AI models.OpenViewAI Decision ReviewsEvery AI-assisted employment decision a person must review: a resume score or a candidate summary made under suggest-only. Accept it, override it with what you decided, or reject it — with your reason, on the record.OpenReportAI UseEvery use of AI and automated decision tools in the last 90 days, and every refusal: ASK questions, agent runs, resume scoring, AI summaries and support auto-answers — who, when, which area, and whether it ran, only suggested or was refused.OpenReportAI Disclosure RegisterEach AI and automated decision tool in the product: what it does, how it is configured here today, what data it uses, who else is involved, and how a person reviews it. Company data is not used to train AI models. Download it for a disclosure or an RFP.Open
Configuration
The company tree, the numbering, the lists, and what this company has added.
Core Settings
5The company tree, the numbering, the lists every module chooses from, and the numbers the platform itself runs on.
WorkspaceCompany StructureCompanies, business units and departments — the dimension every document carries.OpenWorkspaceNumber RangesHow each kind of document is numbered, and whether it is entered by hand.OpenWorkspaceConfiguration ListsThe values every dropdown in the platform chooses from.OpenWorkspaceAI EnginesProvider keys, sealed at rest. Nothing here ever hands a full key back.AdminOpenWorkspaceRuntime SettingsHow long a session lasts before it signs itself out, how many wrong passwords lock an account, how many rows one import reads, how long an administrator may borrow authority for. Every one of these was written into the source and was the same for every installation; they are defaults now, and each one says what it is for.AdminOpen
Classification
5Category sets and their trees, descriptive attributes, and the shared address book — the spine every master stands on.
RecordsCategory SetsA tree with a purpose. Several sets per entity is what stops classification collapsing into one tree nobody can agree on.AdminOpenRecordsCategoriesThe tree itself. The path is materialised, so a subtree is one indexed query rather than a recursive walk on every list.AdminOpenRecordsAttribute GroupsDescriptive attributes whose members vary by category — thread pitch on a fastener, dose form on a drug. Distinct from custom fields: this is what the PRODUCT knows an item can have.AdminOpenRecordsAttributesThe members of a group, with their type, unit and bounds.AdminOpenRecordsAddress BookOne address model, shared by customer sites, supplier sites and workers — three copies of it means three opinions about what a postal code is.Open
Customization
4Fields and logic this company has added: labels for the ten spare fields every table carries, custom fields held in a schema of their own, and the company’s own validations. None of them blocks an upgrade.
WorkspaceAdditional FieldsTen spare fields on every master, transaction and line table — five text, three number, two date — already on every screen, hidden until someone switches one on from a list’s Columns menu or a form’s More fields. Rename one here if you want your own name for it, or to put it on everybody’s screen by default.OpenWorkspaceField RequirementsMake any field of any screen mandatory for this company — header or line, on every save or only before a step such as Submit, Approve or Post — including the fields a later step of the business flow reads. Fields the product requires stay required.OpenWorkspaceCustom FieldsFields your organization has added to any screen, report or dashboard. Stored outside the core tables and joined on, so the product is never modified.AdminOpenWorkspaceCustom LogicValidations, computed values and defaults your organization has written, as expressions evaluated in a sandbox that can reach nothing but the record being saved.AdminOpen
Automation
Work that happens without anybody doing it, at one record or at a million.
RecordsWorkflowsA trigger, a condition and a list of steps. Run one by hand to see exactly what it would do before letting an event drive it.OpenViewWorkflow RunsEvery run, with the step log underneath it. Open one to see which step stopped it and why.OpenRecordsWorkflow ApprovalsA workflow that needs a human waits here. Deciding it releases the run — or stops it.Open
Automation
7What the background jobs found and what became of it, how far each may act by itself, when an approval or a ticket left alone is chased and escalated, and the folders and mailboxes whose documents become drafts.
ViewAutomation ResultsEverything a background job handed over: what it found, the level it was handled at, and what became of it. The people it was for see theirs in My approvals.OpenRecordsAutomation LevelsHow far each background job may go by itself: tell people what it found, ask for approval and then act, or act and tell them. A job with no level here only tells.OpenRecordsTime LimitsWhen an approval or a support ticket left alone is chased, and when and to whom it is escalated. Only what falls due after a limit is written is swept.OpenViewReminders & EscalationsEvery reminder and escalation the time-limit sweep made.OpenRecordsDocument IntakeFolders and mailboxes whose documents become DRAFTS: a supplier invoice, a sales order. Nothing is ever posted; the file is attached to the draft it made.OpenViewIntake LogEvery file intake took in: what it read, the draft it made, or why it needs a person.OpenViewEvent DeliveryEvents a subscriber (workflows, agent triggers, webhooks) could not take: retried with backoff, then set aside after five attempts. Send one again once the cause is fixed.Open
Batch
7Mass functions: the jobs every module runs over many records at once, the run books that order them, and what each run actually touched. A job that takes longer than anybody will wait runs in the background, and one nobody should have to be awake for runs on a schedule.
WorkspaceBatch ConsoleThe job library for every module, with a rehearsal that shows which records a job would touch before it touches them.OpenRecordsJob DefinitionsWhat each job selects, what it does to what it selects, and whether it is safe to run twice.OpenRecordsJob SetsA run book: several jobs in the order somebody would run them by hand, and what to do when one of them fails.OpenRecordsSet StepsThe order of a run book, and which steps may fail without stopping it.OpenRecordsJob SchedulesWhen each job runs without anybody starting it. Every one of these fires in the background as the person who created it, so it may take as long as it takes — which is the point for a large file read off a drive, or a folder somebody drops one into every morning. "State" says whether it is waiting, running, overdue or paused; overdue for long means the API is not running the scheduler.OpenViewJob RunsEvery run that has happened, what it selected, and what it did to each record. A run cannot be deleted — that is the point of keeping it.OpenViewSet RunsA run book executed end to end, including where it stopped.Open
Business Flows
8The chains that cross module boundaries — procure to pay, quote to cash, hire to retire — counted rather than drawn.
WorkspaceFlow MapEvery step of a business flow with the records currently sitting in it, and every handover with how many of them got across.OpenRecordsFlow DefinitionsThe chains themselves. A template ships with the platform; a copy belongs to whoever made it.OpenRecordsFlow StepsWhat each step is backed by, and what "still in this step" means in the words the table itself uses.OpenRecordsFlow HandoversThe column that carries each link. Without one an edge can be drawn but not counted, and the map says so.OpenViewFlow SnapshotsThe shape of a flow on a given day, so a slide from 8% stalled to 21% is a record rather than a memory.OpenRecordsTest ScenariosAugmented data for a flow, made by calling the same routes the screens call rather than by inserting rows behind the application’s back.OpenRecordsScenario StepsThe call each step makes, with tokens for the parts that vary. {{ref:module/resource}} picks an existing record; {{prev.x}} takes it from the step before.OpenViewScenario RunsWhat each run created, and whether the flow’s handovers moved as a result.Open
Connectivity
What is published to other software, what is connected in, what reaches out, and what money and public comment come through.
Published API
6What this company allows to leave it, and who may come and get it. Nothing is reachable from outside until somebody publishes it: one screen, its columns and the rows of it that may travel. Software is then registered, given a key, granted specific exposures and pinned to the addresses it may be used from. The same publication serves a REST API, an OpenAPI document generated per key, and an MCP server for an AI agent.
WorkspaceAPI StudioOne board for the whole of the published API: what is exposed, who holds a key, what each key could not actually do, and every call made in the last few days with the reason for each refusal.OpenRecordsExposuresA decision, taken once, that one screen may leave this company — which columns of it, which rows of it, and whether anything may be written back. Nothing is reachable from outside until it is published here, and there is no "publish everything".OpenRecordsAPI ClientsThe outside software that holds a key to this company. Every call it makes runs as a named user here, so nothing it can reach is anything that user could not already reach. The key is shown once when it is issued and never again.OpenRecordsAPI GrantsWhich software may reach which exposure, and with which verbs. Two partners can hold keys to this company and reach entirely different data; withdrawing one changes nothing for the other.OpenRecordsAllowed SoftwareWhere a key may be presented from: a browser origin, a host, an address or a network. A key that requires an allowlist and has no entries reaches nothing — "no addresses named" reads as "not reachable yet", never as "anywhere".OpenRecordsAPI Call LogEvery call made with an API key, allowed or refused, with the reason for each refusal. This is not the audit log — that records what the record actually did, because a published call goes through the ordinary route and the ordinary route audits itself. This records what was asked, from where, and by which key.Open
External Accountants
1Letting the firm that keeps your books in, without giving them a standing login. One invitation creates everything they need — a console user with no password, a key for their software, read-only access to the ledgers a practice reads — and hands you one code to send them. They then open this console in a window that expires, reaches only what you allowed, is read-only unless you said otherwise, and records every call. You can see who is in your books right now, and put them out.
RecordsConnector CatalogWhat can be connected to: protocols, ERP and finance systems, CRMs, identity directories, payment engines and clinical interfaces. Microsoft Teams calls, meetings and presence are not set up here: add them under CRM › Interaction Centre › Connected Channels.OpenRecordsConnectionsA connector configured against a real system — over HTTPS, or directly over the network (a VPN or interconnect) to a database, directory or service port. Every handshake is TLS 1.2 or higher and the server is verified, against a trusted root or a CA you upload under Certificates. Credentials are encrypted on the way in and never come back out — only the last four characters are ever shown. A connection here carries data; it does not place Microsoft Teams calls or create meetings — those run through CRM › Interaction Centre › Connected Channels, and testing a Teams connection here says what that still lacks.OpenRecordsCertificatesCertificates a connection trusts or presents. A trusted CA lets a connection verify a server whose certificate your own authority issued; a client certificate is presented to the server (mutual TLS). What a certificate says about itself is read from it. A private key is sealed on the way in and never shown again.OpenRecordsData PipelinesExtract from a source, apply the field mapping, load to a destination. An incremental pipeline remembers where it finished and starts there next time.OpenViewPipeline RunsWhat each run read, staged for its destination and failed to stage, and where the cursor moved to. Whether the destination itself can be reached is shown by its connection’s health, on Connections.Open
What this company sends by email, to whom, and what became of it. Every message goes from noreply@tranxact.ai unless you send from your own domain. An account being created, a requisition raised, a purchase order waiting for its approver, a ticket answered — each event has a default audience, and a rule of your own replaces it.
RecordsEmail SettingsThe sender and the way mail leaves. "Platform" sends through this deployment’s own Microsoft 365 account as noreply@tranxact.ai. Choose Microsoft 365, SMTP or a mail provider to send through your own account and domain instead — the credential is sealed on the way in and never shown again. A company has one set of email settings: open it, press Edit, then Set credential and Send a test.OpenRecordsEmail RulesYour own decision about an event: who receives it and in what words. Any rule for an event replaces its default, so an inactive rule is how an event is switched off. Any screen’s <module>.<screen>.created, .updated or .status_changed can have a rule.OpenViewEmail EventsEverything the product sends by email, and who receives it when you have written no rule.OpenRecordsSupport CopyEvery step of every support ticket — raised, answered, assigned, escalated, resolved, closed — sent by email to the support desk within a minute of it happening. support@tranxact.ai unless you change it. Only what happens from the moment copying began is sent, and internal notes stay inside unless you tick them in.OpenViewEmail OutboxEvery message: to whom, about what, and what the mail server said. A failed one is retried on its own; a held one goes as soon as a transport is configured, unless it is three days old by then.OpenWorkspaceEmail SuppressionsEverybody who pressed Unsubscribe in an email, or was unsubscribed for them. An address here is sent nothing by any company in this system, except a message the person asks for themself to get into their own account. Re-subscribing one needs a reason, and is audited.Open
RecordsWebhooksEvents pushed out to another system, signed with HMAC-SHA256 so the receiver can prove where they came from.OpenViewWebhook DeliveriesEvery event sent to a webhook, with its signature and what the receiver answered. One that did not go is tried again, waiting longer each time, up to the webhook's retry limit and never more than a day after it was queued. One that failed in the end can be sent again with Redeliver.Open
RecordsPayment EnginesStripe, PayPal, Adyen, Visa, Mastercard and the rest. The published rate is what the fee is calculated at, and takings post to the clearing account rather than sitting in a table.OpenViewTransactionsEvery authorization, capture and refund, the fee taken out of it, and the journal it produced.OpenReportSettlement SummaryGross, fees and net by engine and currency — what was taken against what actually arrives.Open
Social Channels
2The social accounts this company listens through, what each one watches for, and the thresholds applied to everything that arrives. The signals themselves are worked in CRM → Social Desk.
WorkspaceSocial AccountsThe networks, review sites, forums and feeds this company listens to — what each one watches for, how a signal is scored, and what happens to one without being asked. Credentials are sealed; nothing here ever hands one back.OpenReportCollection RunsEvery time TRANXACT went and looked, including the times it found nothing — because "we heard nothing" and "we never asked" are different facts.Open
Data & Documents
Where files live, what leaves as paper, and the shapes and sets generated here.
Drives & Files
2Google Drive, OneDrive, SharePoint, Dropbox, Box, Amazon S3, Azure Blob Storage, Google Cloud Storage and WebDAV — the places this company already keeps files. Connect one and every screen that wants a file can take one from it, and anything TRANXACT produces can be written back to it.
WorkspaceConnected DrivesWhere this company keeps its files — Google Drive, OneDrive, SharePoint, Dropbox, Box, Amazon S3, Azure Blob Storage, Google Cloud Storage or any WebDAV server. Connect one here and it is available to the Import button on every list, to the migration cockpit, and to anything with an export to write back.OpenReportFiles In & OutEvery file that crossed between this company and a connected drive, which way it went, what it was for and who moved it. A door with no record of who used it is not a control.Open
WorkspaceContent SourcesThe same connections as Drives & Files, plus chat and feeds, seen as places DOCUMENTS come from — and what inspection does to a file on the way in. To connect a drive so screens can read data files off it, use Drives & Files.OpenReportLinked DocumentsEvery document TRANXACT holds or points at, what inspection made of it, and whether anything has read it.OpenReportDocument LinksWhat is attached to what, across every module.OpenReportAttachment SuggestionsWhat reading the attachments turned up — mismatches, risks and gaps, most pressing first.Open
Printed Forms
2The invoice, the cheque, the purchase order and every other document this company sends out — drawn on the page rather than written in code. One of each ships with TRANXACT carrying the TRANXACT mark; upload your own logo under Personalize and every form takes it, without any of them being edited.
WorkspaceForm DesignerDrag fields onto a page and that is the form. Millimetres rather than pixels, because a cheque printed from a design done in pixels is a cheque that is 3mm out. The preview is the real renderer, not a drawing of one.OpenReportWhat Was PrintedEvery document produced, which form it used, how many pages came out and what the render could not do — a blank VAT number is a question with an answer.Open
Electronic Signature
2What this company signs electronically, who may sign it, and every envelope that has gone out.
WorkspaceSignature EnvelopesEvery document this company has sent for signature, in every module: what was sent, who has signed it, who is still holding it up, and the signed copy.OpenWorkspaceE-Signature SettingsHow long a document stays open for signature, how often a signer is reminded, which documents may be sent at all, what a signer agrees to, and the signing limit each person or role holds.Open
Data Retention
3Archive or purge data once it is old and nobody has touched it for a while — both periods, how often it runs, and archive or purge, are yours to set. Nothing is shipped: with no policy, data is kept for ever. Archived records can be read and put back; purged ones cannot.
RecordsRetention PoliciesArchive or purge one kind of data once it is older than the years you set AND has not been added to or changed for the years you set — then again on the period you choose. There are no defaults and none is shipped. A policy starts switched off: preview it, then switch it on. Records something else still refers to are kept and counted. Purging needs the delete permission on this screen.OpenViewRetention RunsEvery run of every retention policy — scheduled, run by hand, or previewed — with what it looked at, what it archived or purged, and what it kept and why.OpenViewArchived RecordsWhat archive runs took out of the live tables, each with the rows that went with it. Restore puts a record back exactly as it was — refused as a whole if anything it refers to has gone since.Open
Records & Legal Hold
3Hold what a matter may need so nothing can change or destroy it, and export everything about a person, a matter or the company.
RecordsLegal HoldsA matter — litigation, an audit, an investigation, a public records request, a grievance or a complaint — holds the records it may need. While a hold is active the records it reaches cannot be changed, deleted, archived or purged, and their files cannot be deleted: the database refuses, whoever asks. Name the people (employees, applicants), the document types, the dates and, if you want, only some tables. A hold is never deleted; Release ends it and both stay on record.OpenViewRecords ExportsEverything about one employee, one applicant or one legal matter — or the whole company — as one ZIP: every record as JSON and CSV (and XML and Excel for a person or a matter), its audit history, its attachments from the document store, a manifest with a SHA-256 of every file and a PDF summary. Built in the background; every request and every download is audited. Passwords, keys and tokens are never exported.OpenReportHold CoverageEvery table a legal hold can reach, the columns that name a person in it, the document type and date a hold reads, and the bookkeeping a held row may still have changed (a file moving to the document store, a virus scan). Every HR and recruiting table that names an employee, a person, a candidate or an application is covered.Open
Synthetic Data
2Data that never belonged to anybody: generators fitted to a real table, and what each run produced.
RecordsSynthetic Data GeneratorsA statistical generator TRANXACT fits and runs itself, or an endpoint at a service hosting a trained model. Every run says which produced it.OpenRecordsGeneration RunsWhat was produced, how close it came to the real distribution, and how much was withheld for sitting too near a real record.Open
Data Quality
4Duplicates found by the weekly scan, the rules good master data keeps, what breaks them, and merges a data steward approves.
RecordsDuplicate CandidatesCustomers, suppliers, items and employees that look like the same thing entered twice, found by the weekly scan from name similarity and shared identifiers. Decide each: not a duplicate, or propose a merge.OpenRecordsQuality RulesWhat good master data looks like, one rule per field: required, a format, a range, or a reference to another master or a configuration list. Checked every night; each break is a finding.OpenRecordsQuality FindingsEach record that breaks a quality rule. A finding closes itself when the record is fixed and the rule is checked again; waive one that is right as it is.OpenViewMerge RequestsTwo records that are one, waiting for a data steward. Approving re-points every reference to the record that stays, in one step, and keeps the other (inactive) so the merge can be undone.Open
Insight
Governed datasets, the numbers defined once, and the catalog over them.
RecordsDatasetsA governed view over the estate, defined once and used by every metric and query built on it.OpenRecordsMetricsOne number, defined once, so the same question gets the same answer everywhere. Whether higher is better decides whether the target is met.OpenRecordsSaved QueriesAd-hoc analysis that anyone can re-run. Only SELECT and WITH are allowed, one statement at a time, capped and timed out — and every run is logged, including the ones that were refused.OpenRecordsDashboardsTiles over metrics and saved queries. Render one to see the current numbers; a tile that breaks reports its error without taking the rest down.OpenViewQuery LogWho ran what, how long it took and how much came back — including every statement the guard refused. Append-only.Open
ReportReports & AnalyticsThe report catalog for this module, and the models behind it — dimensions and key figures you can rearrange, filter, total and export.OpenReportPredictive & PrescriptiveWhere this module’s measures are heading, how much that projection is worth, and what to do about it while there is still time.Open
Operations
Coming across from the old system, whether this one is well, and what it is licensed on.
Legacy Migration
10Bringing a company across from the system it is leaving — masters and open transactions through the application, closed history archived rather than re-posted.
WorkspaceMigration CockpitThe cutover as a numbered plan, one step at a time: where in the old system each extract comes from — with the program or query to produce it — then upload, read the rejections, and load, post, archive or post the balances.OpenWorkspaceMigration ReadinessGo-live readiness per business area — ERP, CRM, supply chain, manufacturing, HR, healthcare, student and staffing: records, data quality, exceptions, reconciliation and a status for everything each area has to bring across.OpenRecordsSource SystemsThe systems TRANXACT knows how to be migrated from, and how data gets out of each.OpenRecordsMigration ObjectsWhat comes across from each system, what it is called over there, and which of the three kinds of data it is.OpenRecordsField MapsHow a field becomes a field. The transform is where a SAP date, a German decimal or an X-means-blocked flag is dealt with.OpenViewMigration BatchesEvery consignment of rows, with what became of each.OpenViewMigration RunsValidate, load, archive and balance runs. A run cannot be deleted — it accounts for records that now exist.OpenViewMigration ResetsEvery time a company’s cutover was started again, and what it took with it. Kept because the load runs a reset deletes were what accounted for records that now exist — so this is the only trace a wipe leaves.OpenViewArchived HistoryClosed documents from the old system, kept whole and addressable by their old number. Records, not transactions: nothing here has been posted.OpenViewOpening BalancesThe one thing the old ledger puts into this one, as a single conversion entry on the cutover date.Open
Health
6What the platform is doing this second — every request, background worker and batch run with the database work behind it and the locks it holds — and whether the integrations, pipelines and workflows are healthy. Cancel a runaway query, release a stale lock.
WorkspaceWork ProcessesEvery request, background worker and batch run on every container, each tied to the database backend it is using, and every backend tied back to the work that sent it. Cancel a runaway statement or end a stuck backend.OpenWorkspaceSystem TracesOne process in full: every statement it sent with timings, the locks it holds and waits on, who it blocks and who blocks it, and the plan of what it is running. The slowest recent work and the statements with the most database time.OpenWorkspaceLocksLocks being waited on, locks that block others, advisory locks and batch runs that still say running — which are stale, and releasing them.OpenReportIntegration HealthEvery connection, when it was last tested and whether it passed.OpenReportPipeline HealthRuns, failures and throughput per pipeline — the ones to look at are at the top.OpenReportWorkflow HealthWhich automations are firing, which are failing, and how long they take.Open
License
2What this installation is licensed on — a percentage of the revenue filed with the tax authority for the prior year, or the gigabytes of data it consumes — and the meter behind it: data in, data out, disk, data processed by the database and AI engines, and backups, each measured continuously. The basis changes only with a new license key from TRANXACT.
WorkspaceLicense & MeteringThe license in force and the fee it implies, and the data units this installation has consumed — incoming, outgoing, persistent disk, processed and backup data — this month, day by day and for each month before it. Read-only: the license changes only when a new key from TRANXACT is applied.OpenWorkspaceBackupsThe backups this installation holds of its own data, what each one weighs on the meter, and deleting the ones you no longer need.Open
More
Reachable by link
2These screens carry no tile on the module page. They are reached from the record they belong to, from a saved view, or by their address — and they behave like any other list once open.
RecordsIdentity Providers (raw)The connection table behind Single Sign-On, as rows. Edit connections under Access → Single Sign-On, where the protocol decides which fields you are asked for.OpenWorkspaceSigned In NowOne row per live session rather than per person, so somebody working on a laptop and a tablet appears twice. Ending one stops the token working on its next request — which is what “sign out” never used to do.AdminOpen