It is absolutely possible, when you authenticate a user (EAP-PEAP or EAP-TLS), you can check the access tracker to discover all AD attributes of that client, including group membership. you can use those attributes in your enforcement policies to apply different profiles to each user.
Please be aware that when you start in vlan A on machine auth, and after user auth the vlan is swapped to VLAN B, this can cause problems because the client will request a new ip adress. This can cause disruptions during log on.
A better way is to work with roles, assign a role with certain acl's on machine auth, and assign a new role on user auth, this role is placed in the same vlan, but with other ACL's. This way the machine stays in the same L2 network, and you only change the role/policies for that user.
If you do not want to work with roles on the switch you could use downloadable ACL's for normal radius authentication, but i advise to work around the vlan swapping during login.
for details about configuring this, check out this guide:
https://community.arubanetworks.com/t5/Security/ClearPass-Solution-Guide-Wired-Policy-Enforcement/td-p/298161