Access Codes and Custom Fields
Summary: Sandy Harrison inquired about using a singular access code for a job and the ability to rename custom fields. Felecia McGowian (Captura) explained that a single code is possible with a Standard job, but not with a Subject job, and noted that custom fields cannot be renamed currently. Tearah Fox (Captura) added their studio to a feature request and discussed job setup options, offering personalized settings and inviting them to onboarding events for further guidance. Sandy Harrison expressed interest in pursuing these options and participating in the events to better integrate the suggested solutions.
Hi! I Have two questions that I've searched for answers and haven't come across them yet:
I'd like to set a singular access code for a job so that each subject doesn't need their unique online code to see the shop.
The only job configuration checked is "Subject"
Type is set to Event
I can see where to edit online codes, but nowhere to change an overall access code
Can custom fields be personalized in any way?
This may not be a feature, but it would be incredibly helpful to be able to rename the custom fields for workflow-wide use.
During photoshoots, we currently have to reference cheat sheets that list the values (ex. custom1 = SSN, custom2=Rank, custom3=...etc). If the custom values were renamed, it would cut down on time taking subject information and remove the need to reference a separate sheet with the values written down.
Any advice or work-arounds would be appreciated. Thanks!
Lara J.
Tearah Fox (Captura)
Admin3 weeks agoHi Sandy,
I have added your studio name to the existing feature request for the ability to name your own custom fields. This feature has not yet been scheduled but has been recorded. in our backlog of ideas.
Can you confirm if you want the jobs setup with a single access code as a pre pay or a proofing job? There are definitely a few ways to set these kinds of jobs up but it would differ depending on pre pay verse proofing and how you need to manage any post production.
If you turn up to this weeks onboarding events with Nate (in particular Wednesday when we go over jobs) we can talk out your specific scenario and show you your options in real time.
Either way if you confirm the prepay or proofing I can write up specific settings for you to try :)
Sandy Harrison
OP2 weeks agoHi Tearah, thanks for your reply!
We want the job setup to NOT be prepay (we take payments and input orders immediately after capturing subject photos). I don't think I quite remember what the "proofing job" entails, but we definitely would rather set it up as that instead of pre-pay.
Any specific configurations and settings to help our process would be very appreciated. We'll also look into doing those onboarding events so we can freely talk with each other.
Tearah Fox (Captura)
Admin2 weeks agoA standard job can accomplish what you need.
You can technically also choose to set up a subject job and just place everyone underneath one subject, record sharing the access code to all.
@Mark Quintilio (Captura) had some good insights into why one way might be better than the other. Any chance you can chime in, too, Mark, with some advice?
Mark Quintilio (Captura)
·2 weeks agoHey Tearah and Lara.
Tearah's suggestion to create a subject job with one subject and have all images loaded under that image can be a good option. The key reasons for this type of set up would be:
subject jobs have access to the image edit tab - currently standard jobs do not.
subject jobs would allow you to separate individual and group photos more efficiently
subject jobs offer the ability to edit orders prior to release where standard jobs do not
Certainly both options can work, but those would be my key take aways.
Felecia McGowian (Captura)
·3 weeks agoHi Sandy!
For your first question, if you'd like to use a single access code for the entire job instead of unique online codes for each subject, the job would need to be set up as a Standard job. With a Subject job, each subject is assigned their own unique online code for access. For the subject job, codes can't contain duplicates.
As for your second question, custom fields cannot currently be personalized or renamed. They are fixed as Custom1, Custom2, Custom3, etc. I agree that being able to rename them to match your workflow (e.g., SSN, Rank, Unit) would make data entry much more efficient and eliminate the need for reference sheets. That would be a great feature request for future consideration.
I hope that helps!
Sandy Harrison
OP2 weeks agoHi Felicia,
Thank you for the clarification! We'll look into integrating Standard Jobs into our process instead, as that would more closely align with how we market to clientele. Thanks!