Skip to content
Ayush Agro Foods

Integration · Identity and sign-in

Ayush Agro Foods with Okta, read-only.

If your team signs in to tools through Okta, Ayush Agro Foods reads which apps each person is assigned and when they last signed in to each, through an Okta API service app with read-only scopes. Deactivated users start an offboarding sweep.

  • Read-only
  • 3 permissions listed below
  • Disconnect at any time
Connect OktaIdentity and sign-in
Ayush Agro Foods is requesting3 permissions, read-only
  • okta.users.readThe people list and each person's status. Deactivation is an offboarding trigger.
  • okta.apps.readThe apps configured in Okta and who is assigned to each, which is the paid-seat side for SSO tools.
  • okta.logs.readSystem log sign-in events, to find the last time each person signed in to each app.

Never read: passwords, factors or authenticator enrolments.

What moves, and which way

What Ayush Agro Foods reads from Okta, and what it writes.

Reads into Ayush Agro Foods

  • Users: name, work email, department and status (active, suspended, deactivated)
  • App assignments: which tools each person has been given through Okta
  • System log sign-in events per app, to find the last sign-in date per person per tool

Writes out of Ayush Agro Foods

  • Nothing is written into Okta

Permission scopes

Exactly what is requested, and why.

Your admin sees the same list on the consent or setup screen. Anything not listed here is not requested.

Scopes for every integration
Permission scopes requested for Okta
Scope or routeWhy it is needed
okta.users.readThe people list and each person's status. Deactivation is an offboarding trigger.
okta.apps.readThe apps configured in Okta and who is assigned to each, which is the paid-seat side for SSO tools.
okta.logs.readSystem log sign-in events, to find the last time each person signed in to each app.

Setup

4 steps, usually done on the onboarding call.

  1. 01

    In the Okta Admin Console, create an API service integration for Ayush Agro Foods, or add Ayush Agro Foods from the steps Ayush Agro Foods shows you.

  2. 02

    Grant only the three read scopes above and assign a read-only admin role to the service app.

  3. 03

    Paste the client ID into Ayush Agro Foods and complete the key exchange.

    No Okta admin password is shared.

  4. 04

    Ayush Agro Foods reads users, app assignments and 90 days of system log events, then reads new events daily.

Never read

  • Passwords, factors or authenticator enrolments
  • Policies, network zones or admin settings
  • Any write action: groups and app assignments are read, never changed
  • Activity inside the tools themselves

Questions about Okta

Ask the team

How long does Okta keep sign-in history?

Okta's system log retention is set by Okta for your plan. Ayush Agro Foods reads what is available on the first connection and keeps the last sign-in date per person per tool from then on.

Can Ayush Agro Foods unassign apps when someone leaves?

No. The Okta connection is read-only. The offboarding sweep lists each tool and your team confirms when access is removed.

Do we still need Google Workspace or Microsoft 365 connected?

No, but most companies connect both: Okta for SSO tools, and Google or Microsoft for the people list and email-based sign-ins.

Connect Okta on the demo call.

We set up the first connection with your team and show the tool list, seats and renewals it produces.

  • Read-only access
  • Data hosted in India
  • Priced in rupees
  • 14-day trial on your data