YeboID

consent permissions

See what the app wants. Choose what you share.

Before an app gets your information, see what it is asking for. The request might include your profile, verified email or KYC status.

Read about app permissionsWatch the YeboID overview

YeboID overview

One person, more than one role45 sec · English captions
Read the video transcript

One person, a carpenter looking for work, a shop owner selling what he makes, a manager acting for his business. Yebo ID gives him one identity across connected services. He starts with his phone, confirms it's his, and sets a pin. Another service asks for access. He sees what it wants and chooses which business to share. His identity continues. The permissions stay specific. Connected services can receive his verification status when he allows it. Google-style sign-in for Africa, built for the person and the business. Yebo ID, one identity for how Africa works, trades, and builds. Bring Yebo ID into your service.

How to get started

  1. Open the app connection.

  2. Read the requested permissions.

  3. Choose whether to approve.

  4. Continue with that choice.

Know the request

See the application and the information it wants before you approve the connection.

Keep choices separate

The permissions you give one app do not automatically apply to another.

Share for a purpose

An app should request the information its service needs. Developers must keep use within that permission.

A few useful details

Check the permissions and decide whether to continue. A different app makes its own request, even when you use the same YeboID.

A product needing your verified email asks for that permission. You can read the request before deciding whether to connect it.

The permissions shown depend on the app. App roles and company access are separate from identity sharing.

Ready to try it?

Read about app permissions

More from YeboID

Single sign-on

Use your YeboID across connected apps, with a separate permission choice for each one.