The employee portal: what everyone can use, and an answer within a day.
Each employee sees what exists for them and requests a tool in one click. You receive the request with its context and you decide.
What an employee sees
- What is available to them, what is allowed, what isn't.
- The rule next to the tool: for each piece of software, the data fact sheet says what it does with content and whether a protected version already exists.
The request that waits
An AI tool request that waits means a blocked employee, a person approving without information, and usage that happens outside the process in the meantime.
- The employee writes the request, on the page or in Teams.
- Ojja recognizes the tool and answers right away when the answer exists: already available, an equivalent already paid for, or not approved with its reason.
- Otherwise, the person in charge receives the fact sheet: equivalent already paid for, hosting, training on data, model, list price, linked frameworks, points to review with your counsel.
- They decide. The decision enters the register, the employee is notified, and the answer applies to the next requests.
A tool request gets an answer within a day, and its fact sheet first shows the equivalent you already pay for.
Each pending request stays visible, with how long it has been waiting.
The one-day answer applies to tools already in the catalog; for a tool that is not in it yet, the verification time is shown.
What the portal does not do
- Ojja turns nothing on, assigns no seat and recommends no purchase.
- Asking is not getting: your company decides.
- The counts reported are aggregated by tool and by department, never by person.
The other Ojja Watch features
The AI register
Each AI feature has its line, its status and its source.
The AI fact sheet
What each feature does, what it reads, where the data goes.
Worth its price
The time each tool must save.
Decide
Five verbs, a register, a snapshot that records.
Your feed and alerts
What changes at your vendors, filtered on your tools.