Now in the right channel og: Hi, is it possible to...
# permit-saas
j
Now in the right channel og: Hi, is it possible to use the Frontend Components without exposing any user data outside our own VPC ? Clarification: I'm talking about e.g. this: https://docs.permit.io/embeddable-uis/element/user-management How would the element know how the user is called if I only provide a user ID ?
a
Hi @Jannis Köksel, I'm an AI assistant for Permit.io. I'll analyze available sources and get back to you shortly.
p
Hey, thanks for reaching out ! It seems our team is a little busy right now, a human will be with you within the next hour or so. In the meantime, can I help you ?
a
Yes, you can use Permit Elements with the FrontendOnly login method, which keeps authentication within your control (1) . With this approach, you pass a JWT containing the user information directly from your frontend . Here's how it works: 1. You configure JWKS in your Permit environment (2) 2. Your JWT's
sub
field matches the Permit user key 3. You use the FrontendOnly login method (1) :
Copy code
permit.elements.login({
  loginMethod: LoginMethod.frontendOnly,
  userJwt: "<YOUR_USER_JWT>",
  tenant: "<YOUR_TENANT_KEY>",
  envId: "<YOUR_ENV_ID>",
})
The element gets user information (name, email) from your JWT - you control what data is included (2) . The JWT stays in your frontend, and only the necessary authorization checks go to Permit's infrastructure. For the User Management element specifically, you can configure whether to display user email, full name, or both (3) (4) . This display configuration is separate from the authentication flow. If you need complete isolation, you could also consider the server-side login methods with custom headers or bearer tokens (1) ,
To learn more, see the sources I considered: [[1] Login Method](https://docs.permit.io/embeddable-uis/element-login) [[2] Embedding Elements](https://docs.permit.io/embeddable-uis/embedding-elements) [[3] User Management Element](https://docs.permit.io/embeddable-uis/element/user-management) [[4] Permit Elements](https://docs.permit.io/embeddable-uis/overview)
t
AI had a good answer. Does that make sense?
j
Somewhat, from what I'm gathering, is that email or username need to be stored within permit for the element to work
p
Hey, thanks for reaching out ! It seems our team is a little busy right now, a human will be with you within the next hour or so. In the meantime, can I help you ?
j
Is there a list of data requirements for each element ?
Im taking about the users being managed, not the one doing it
o
As with anything in Permit, the only thing you need for a user is a unique ID, which can be opaque. You need to provide an email only if you want us to send an invitation to the user for you