Editing user data in the UI
-
Hey guys, I thought you could edit user data in the UI now? Would be really great if you could just edit the JSON in the UI directly for user data.
-
You can edit user and registration data in the admin ui. This is handled using forms, each tenant and application can be assigned a custom form to edit a user or user registration respectively.
More details here: https://fusionauth.io/docs/v1/tech/guides/advanced-registration-forms/#editing-user-data-in-the-admin-ui
We’ve discussed allowing direct JSON editing. It is too error prone.
Perhaps in the future we could enable a “danger - expert only - no fences” mode and allow it. Using the forms we can perform custom validation, type safety, etc.
-
@dan It doesn't seem fair that you can't modify a form without a license. I don't need to do anything elaborate, just rearrange some of the fields in the Admin User Form, delete fields I'm not using, and add the firstName field to the form. firstName should be one of the standard fields anyway.
-
@dan wanted to ask about the templates/UI piece - are there any plans to offer just the ability to edit the template UI as a monthly service fee?
While I disagree with the comment above with it being 'unfair' (don't really see any unfairness with a free software not offering all the bells and whistles), it is quite a ramp from the free to starter plan offering. I would think an intermediate stage tailored towards towards needs of the hobbyist/small start up wanting to demonstrate UX/UI cohesion in a prototype using the auth system would translate into more conversion into the starter plan once those apps are brought to scale/the premium auth/mfa features are necessary.
-
Hi @brad ,
Thanks for your feedback. I appreciate hearing from folks using the product on how we can improve it. We've made a business choice to release some features only for the paid version, while making a full featured free version available. (I always say "we like to eat just as much as the next person, and that requires charging for something"
). I'm sorry this feature set doesn't work for you. I outline a zero-cost workaround below, but if that doesn't work for you, I understand. We would love for everyone to use FusionAuth but know we can't always be the best solution for everyone.Hi @anna ,
There's no plans to offer the ability to modify forms in the community edition, but you can absolutely stand up a small application using one of the client libraries and an API key. This application can modify user data using the API in whatever way you'd like. That's the typical workaround when folks find that jump in price too much.
Thanks!
-
@dan I understand you need to eat and most of the paid features make sense as only being available to paying users. The paid version has "Advanced Form Editing" capability, which I'm certainly not expecting. However, restricting the ability to add/delete built-in fields from the default form, seems too crippling for a product advertised as "full-featured, even in the free version".
Why not restrict it to simply adding/deleting/rearranging the built-in fields in the default form, without the ability to create custom fields or custom forms? That would still maintain a big difference from the free version to the paid version in terms of form customization capability, but it would make the free version more useful to its intended audience. Some fields like Birthdate, Languages and Username are useless to us, while the First Name field is conspicuously absent. I understand we can workaround the issue using the API to edit user profiles, but it seems like absurd overkill to create a custom external form just to add a First Name field and get rid of a couple of useless fields.
I assume the reason you offer a free version is to gain exposure for the product, and also in the hopes that some free users will eventually upgrade to become paying users. Therefore, restrictions on true enterprise-level features make sense. However, arbitrarily crippling the ability to edit the default profile form makes no sense to me and detracts greatly from the product.
-
@brad Hi Brad,
Thanks for the feedback. I hear your frustration.
One note of clarification: in the admin UI, you can edit the first name field, but that field exists on the user editing form, not the registration editing form.
Here's more documentation about that.
If that doesn't work for you, then I'm afraid there are two options:
- build your own UI, as I mentioned above
- find a different product. We'll be sorry to see you go, but understand FusionAuth doesn't work for everyone
-
@dan This is the main point of my argument. The field does NOT appear on the user editing form, but it obviously should:
-
@brad Hmmm. That's a bit weird, as I see it in my instance on both the add and edit user screens in a sample FusionAuth instance. I can see why that would be a suboptimal experience.
Edit screen:
Add screen:
A few questions for you.
What version of FusionAuth are you running?
If you download and install FusionAuth locally, do you see the first name field?
Where are you running this instance of FusionAuth?
What browser are you using (and do you see the same behavior from all browsers)?
Is the field in the HTML and hidden or not present in the HTML?
Thanks.
-
I'm running v1.47.1. It's installed on a Ubuntu 22 server from your Debian package. I'm using Chrome, but the field is not present at all in the HTML, so the browser wouldn't matter. I haven't installed it locally, but I'm not sure what that would prove. The field shows up for you, so clearly it's supposed to be there. Perhaps the issue is specific to the Debian package. Everything else works fine, so I assume it was some oversight during the build process.
-
@brad Gotcha. That is bizarre behavior. But I just installed the debian package on a VM with mysql and can replicate. I filed a bug, and you can follow it.
-
@dan Thank you!
-
@brad This is slated to be fixed in 1.49, the next release. More details in the GH issue.
-
@dan I'm now on 1.53.2, but the First Name field still doesn't appear on the User Profile form. I noticed in the Github issue, they wrote:
We are naming the user.firstName field [Admin Registration : first name instead of [Admin User] first name so when we go build the default form we don't find a result because we look up the field with WHERE name = '[Admin User] first name'.
Therefore, I changed the field name in Customizations->Form Fields to [Admin User] first name.
Next, I edited the form and added the field. However, when I try to save the form, it says:
To modify a form that is currently in use must activate the Reactor with a valid license key.
When I navigate to the Reactor page, it shows that it's licensed with a Community Edition license.
-
When I navigate to the Reactor page, it shows that it's licensed with a Community Edition license.
Custom form fields require a starter license, and because you modified the form field names, FusionAuth thinks you are trying to use a custom form field. (Note, I'm not suggesting you buy a license--this functionality should work in community edition--but I wanted to explain why you are getting the message.)
With the move to 1.53.2 did you upgrade or use a new instance? If the former, does the issue still appear in a new install?
-
I upgraded. I haven't tried a new install nor do I want to. I understand why it's happening. Is it something you can fix in a future update, without my having to start over with a whole new install?
