Every Confluent identity, including the service accounts

Human users, service accounts and the organisation role bindings behind them, read into Ploy.

Book a demo

TYPE · SAAS

Confluent connectorHOURLY SYNCCAPABILITIES

WHAT PLOY DOES

Discover users, invitations and service accountsEvery identity in the Confluent Cloud organisation: people, invitations nobody has accepted yet, and service accounts.

READ

Read whether an account is activeActive, suspended or still pending, so a half finished invitation is as visible as a live login.

READ

Read organisation role bindingsAccess to Confluent itself, with the organisation scoped role binding held as the entitlement. Cluster and topic level access is not read.

READ

Register Confluent as an app in useConfluent lands in the app inventory with its account holders attached. Third party apps connected to it are not discovered.

READ

Invite a new userWhen policy or an approved request grants Confluent, Ploy sends the invitation. The connector runs under the least privilege AccountAdmin role.

WRITE

2.1WHAT IT UNLOCKS

Three jobs this connector does on day one

ACCESS

An approved request becomes an invitation

Policy or an approval decides that someone needs Confluent. Ploy sends the invitation, so the account exists because a decision was recorded rather than because somebody asked in a channel.

REVIEWS

Reviewers see the role binding

Each row carries the organisation role binding behind the access. The decision is about an entitlement, not about a name on a seat list.

SERVICE ACCOUNTS

The non-human identities are on the list

Service accounts and invitations that were never accepted arrive alongside people. They are the accounts an estate usually loses track of, and they sit in the same graph as everyone else.

2.3