Video: Feature Focus: Connecting your team and external stakeholders | Duration: 3672s | Summary: Feature Focus: Connecting your team and external stakeholders | Chapters: Welcome and Introduction (4.48s), Custom Email Notifications (174.91s), Custom Email Notifications (302.80002s), Email Notification Setup (779.3s), Email Subscriptions Setup (1014.66s), Managing Secure Links (1173.345s), Secure Link Implementation (2910.9348s), Secure Link Implementation (3051.905s), On-Demand Video Access (3277.115s), Document Creation Q&A (3381.6548s), Secure Link Redirect (3441.125s), Conclusion and Reminders (3510.45s), Conclusion and Farewell (3610.925s)
Transcript for "Feature Focus: Connecting your team and external stakeholders":
Hi, everybody, and welcome to our webinar today. We'll be getting going in just a few minutes. We're gonna give everyone a couple more we're gonna give everyone a little bit longer to funnel in, and join our webinar. Today, we're going to be talking about, essentially building a better connection between you, your team members, your stakeholders, and the data that you're building in Quickbase. This will be a great introductory session. We're gonna cover a whole bunch of features and things that you could be using as part of your workflow to increase the way that you work together with others. While we're waiting another minute for folks to funnel in and join us for the webinar, I'm gonna throw up a quick poll. I'm curious for those attending here today. How experienced are you with Quickbase? Do you consider yourself some and build it being an app admin? Are you someone who just started building apps? Are you somebody who's, like, a seasoned pro who's been doing this for a long time? I'm just curious to know from our attendees, what do you feel like your skill level sits today? Nice. So we're seeing I'm seeing a good mix so far. We've got a few people who are got a good number of people who are feeling confident. They built a few apps. They're familiar with Quickbase. They've got a few newbies. This is great. So session will cover some stuff that will be, very much for folks who are newer to building Quickbase, and they'll see a few tips peppered in and some newer features that you might not, even as a pro, have used yourself yet. And, we'll just see get a few more people funneled in, and we'll get started. Alright. While we're waiting for folks to funnel in, at the end of the day, I have a few, quick notes for folks to help them enjoy their webinar experience. If you are having any issues with your audio or your video, if you look at the very bottom of your screen, there is an option to switch to the light player or light mode. That is a little bit lighter version of our webinar platform. Great for if you're experiencing a little slowdown while you're watching the webinar today. You will see the chat just to the right of where I'm showing the poll. You can use that chat to chat with other people in the webinar today, share your thoughts about what we're covering. You will also see next to that there's a section for documents. That is a bunch of links that link out to help documents and other resources that support the content we're talking about today. And then lastly, there's a q and a section. That is a great place to throw any of your questions you have during the course of our presentation today, especially if you wanna make sure that they get covered in our q and a section, which will be at the end of today's webinar. I'll be taking some time to take questions that are submitted from the q and a and go over them for folks. Also, my standard is always let folks know we are recording today's webinar. It'll be available on demand after this. So if you ever wanna review stuff, you will be able to re, revisit this webinar. You can also share it with others if you think there's others on your team who would enjoy it. Alright. So we've given everyone a few minutes to join. I am going to stop sharing the poll, but it will still be available in that poll section if anyone wants to share their experience over the next few minutes. And we're gonna dive into our webinar today. So as I mentioned, today we're here to talk about connecting your team and your external stakeholders. In specific, when we're talking about what we're gonna be covering today, we're going to be looking at custom email notifications, including some options that you may have ignored if you're a long time user or may not be familiar with if you're new, which is setting up personal notifications or using our email to option with within a report or a form, document creation, sharing your app publicly, or for those of you who are long time users, this is called you might also be familiar with this as EOTI or everyone on the Internet of sharing your app. And lastly, secure links, which is a feature that we launched last year that people are still getting used to that allows you to open your app up a little bit more than you would for sharing your app publicly with a little more security, but not as much as needing to add someone as a user. And then I forgot to add it to the agenda, but as I mentioned, there will be a q and a section at the very end where we will go back and review some of the questions that have come in during the course of the webinar today. Alright. And so for our content today, just wanted to cover some of these features are on different plans. I wanted to make sure clear that all plans had access to the custom emails, the email to, and personal notifications we'll be talking about at the beginning of our webinar today. Everybody on business or enterprise plans will have access to document creation, share publicly, and secure links that, they'll be able to access, on their account with the caveat that share publicly and those of you over long time builders, if you've already used that in your account, you'll continue to be able to use that. Share publicly is just moving to our business enterprise plans for anyone who's a newer customer. If you have those two that option, you're on a team plan. And, also, that's just gonna be the overview of what we're gonna be chatting about today and what plans they'd be available on. So let's dive in today's presentation because I've got plenty for you. So we're gonna go first. We're gonna start out with custom email notifications. So, our email notification is basically break down into two categories that most people find helpful to use. The first one would be a record changing. This is a kind of email that really helps you automate some of the workflows that you use to communicate with members of your team or can be used to communicate to those outside of your organization as well. Whenever a record changes, there's an opportunity for you to set up a notification that will trigger off that change. You can do it when a record is added, when this record is modified, or when a record is deleted, or all three. And you can also build it out to figure out, like, who you want that email to go to on these instances. This is a really simple way to remove a gap where today you might be like, I've built a new project. I put it in Quickbase. I put it in whatever project management services system I use, and I am thinking, oh, okay. Well, now I need to go hunt down the people who are responsible for this project to kick it off. I'm gonna go to my email. Maybe I'm copying and pasting links over. Maybe I'm copying and pasting data over. These really exist to help you get away from the world of you need to manually email people every time a project moves or worse, having projects sit because no one knows that they've changed. And so, like, some common uses for these just to call them out would be, a new project is added and I need people to be aware that it exists. I have assigned a specific piece of a task or a piece of work to a person. I need them to know that they needed to work on that particular record in Quickbase or a particular project, or I have important customers that I'm kind of worried about on the regular and I'm thinking about it constantly. Someone has updated their record to let me know that their status has changed. Perhaps they were thinking about renewing and they were in my renewal flow, and now they said they'd like to have a conversation. I've updated their status to, like, needs contact from my sales team. I don't want that person to sit. This is really valuable and this workflow is really helpful when you're thinking about folks who sit in roles where SLAs or timelines really matter. They are these are the like, your tech support reps who, work for you might really thank you for sending me automatic message anytime a new tech support case is added if they have it to our SLA because it's gonna get their attention and immediately get them on the work. And so these records are really helpful. Are these email notifications really helpful because you're able to set them up, sort of match the workflow that you need, including being able to use filters so that you can say, not only do I want you to message me anytime I I don't specifically just want you to message me anytime someone adds a new project. I only want you to message me if a new project is added and it's and it the urgency field is marked as high. Or I only wanna be notified if I'm the person assigned to the project in the assigned to field. And we'll go over to a little more detail. I'll I'll do a little demo of what these kind of emails look like and how you can configure them. But that's the way to think about these emails. If something happens in my record in Quickbase, someone updates something either manually or through a regular schedule update or an import, I wanna start firing these out to let me know that something has changed and I it needs my attention or my team's attention or vendors or, partners that I work with outside of my organization who I've invited into my apps. And then the other type of email notification that we're gonna talk about today is a subscription email. So while our record changing those are really great for triggering anytime a specific record has changed and meets a certain criteria, Our subscription emails are really helpful for sending a filtered report that you have built on a fixed schedule. You can configure this to send your report, daily, weekly, monthly, yearly even, and you can pick the time of day. For your some of you long time users, you might be thinking to yourself, wait. I have subscriptions already. I haven't been able to schedule the time of day. For our new subscriptions, when you build your custom emails and use new build it myself option, you can designate the time you would like them to send. So rather than having to to stand on the older schedule we had, which was early in the morning on Eastern Standard Time, you can now pick a time of day that makes sense to you. And that's a big, addition to the subscription option. So you're probably wondering, like, what does this mean sending a report on a subscription? Essentially, what this is really focused on is it's allowing you to trigger emails out to a specific audience at a specific time of day that makes sense to you with data that's important. A great example might be every Friday, I want my sales managers to review any customer who, has recently been added. So, like, all so I have a report that shows me all of my new customers for the last month. I can then send that report out to them every Friday as a helpful reminder in their email that says, hey. It's Friday. Please take time before five end of day today to review all of our recently acquire recently closed customer deals and see if any of your team needs to finalize paperwork, review their statuses. You can get more specific. You can get less specific. There's a lot of flexibility here on what you wanna send out. You just basically build the report that makes sense to you in Quickbase, and then you build the filters and trigger that makes sense for you on the subscription email. And you put the two together, and now you've got that email flying out. This can also be really helpful. These emails are really great for if you have leadership who wants to see metrics and they wanna see statuses from Quickbase, but they maybe don't spend all their time in Quickbase, and they don't need to get something every time a record changes. That would be way too much. This allows you to say, like, I'm gonna send them a filtered, focused experience so that they get just the information they need, and then they can go back about the work that they need to do. So you might be wondering, I've never used this feature before. Where do I find them? So in any table that you're in in your app, say you're looking at your company's table, your task table, you can either find it by clicking on the, where this table appears in your side navigation bar and a little dot dot dot and selecting notification subscriptions and reminders or at the top of the page that you're in by hitting settings. If you do go the route of hitting settings, you just have to go and look under the work workflow and permissions header, and you'll find a specific section that says subscriptions, notifications, and reminders. Don't worry. I covered a lot. We're gonna do a quick demo where I'm gonna walk you through what does this actually look like in Quickbase. So I can kinda see it, commit it to memory, and actually feel like I know where I'm going. So if you give me one sec, I'm gonna share my screen with everybody. Alright. You all should be seeing now my contact manager plan application. This is where I'm bringing in new cuss this is where I'm managing companies, contacts, deals that I'm making in order to have a nice workflow where I'm kind of tracking the status of things as they're happening, in Quickbase. And so if I'm thinking to myself, well, whenever a new customer comes in, perhaps I am assigning them to a member of my team so I have an assigned to field. So that way I make sure that that person is sort of the the hands on, the person who makes sure this customer's data has been entered correctly. Their projects are being taken care of. They own the experience with this project with this customer. Could be a sales rep, could be a team lead, a project manager, a customer success manager, like, you have customer success managers like we do. But I just want a simple email to go out. I want them to get a heads up so that they're aware. If I wanted to add something like that, I could go in, grab my notification subscriptions and reminders, and I can see the ones I've built already, who they're owned by, who they get sent to, whether or not they're active. And I even got one already that's you've been assigned to a customer. And so what this email says is that, it goes out whenever project manager is assigned to a customer. So I get to set under our send options. I wanna send a record. I wanna send whenever a record is added or modified, and I can set more conditions if I'd like. In this one, I did decide to choose, more records. I or choose my conditions for triggering. I only wanna send this email if I change the assigned to field. If I'm updating a lot of other information about the customer, I don't want it constantly triggering and sending every time I update a billing date, a contact name. I only want it to send out whenever I change the person who's assigned to the customer. And then in particular, I only wanna send it when they're marked as an active customer. I don't wanna be sending this email for a previous customer who maybe I'm doing a special project with or, people who are still in my leads, like people who haven't become customers yet. It might be surprise it might be a surprise for them and my project manager if the project manager reaches out to somebody who isn't even actually a customer yet. And these work if you've built a Quickbase, report before. These filters are very similar to what you do when you're building a report in Quickbase or when you are building form rules in Quickbase. So you have access to the fields in your application. You have access to a number of different, functions that help you decide that contains is equal to. So you can also do things like only email this out if a deal is over a certain size. Only, send this out if a customer is on a specific plan, for example. You can then choose, I wanna send a single email for all of the changes, or I wanna send an individual email for up to 10 records, or I wanna stop sending an email. What this basically lets you decide is if you are adding a bunch of customers at once through, someone uploading a CSV, running a sync, doing a grid edit, and changing a bunch of set values, do you wanna send an email for every single one? Do you wanna send these emails, kind of grouped together so that they don't aren't as, overwhelming for people's inboxes, or do you wanna not send an email in the case of bulk changes? And then lastly, I we can see some options for, like, permissions. By default, it checks for the permissions of the user you're sending to, so you don't have to worry about if you are sending to a sales rep who's not supposed to see a bunch of data. It will not send that data because it will check first, or you can have it ignore the permissions. If you don't want your rep to be able to see the records live and edit them in Quickbase, but you don't mind if they get an email that one time kinda gives them some information that help that they need to have, but they don't need to change. They don't need to worry about it on a day to day basis. And then lastly, you can compose your email. This is very similar to a lot of, you where if you've, done online blogs, online, tech support portals, you have the options here to sort of stylize, including images. If you're really familiar, you can actually go in and encode yourself to make your email as simple or as fancy as you'd like. You can also use in both the header or both the subject and the body field markers. So same thing, you can pull in any of the values out of your record. That would allow you to pull in k. I wanna include their address, for example, city, state, whatever that that that might be. You can pull that information in. And then lastly, under elements, you'll have an option to do things like show me all the changes that happened to the record, show me the form. Let me pull in a report, as well as sending the data. What this means is, like, for example, this I have here, I wanna include the customer's record when I send it out so that way my project manager doesn't just get, hey. You've been assigned to a new customer and here is their name and here is their contact name and phone number. It instead also says that here's their full information. So anything that's in the record also sends out to them. And that is basically how you would set out a record change email to go out to whenever a record status is updated. We also talked about subscriptions. So for example, in the, use case I was talking about earlier, there is the option for you to send out a recurring schedule. I can say I wanna repeat weekly. There's daily, monthly, or yearly options as well. Pick the time of day and or pick the day and the time. If you are opening up one of your subscriptions or one of your emails today and you are not seeing these options, it is most likely because you are in one of our older subscriptions that existed before we launched our new, option to for building emails. This came out last year. Right be right before the end of the year in October, we launched this. Like or we we really pushed people to our newer option. And so to get access to that, when you're in here, when you hit new email, you wanna use your the build your own option. This didn't exist before we launched our custom emails option. You had these older notifications, subscriptions, and reminders. They all still work. You can still use them. You can still build them. They just don't include the option for scheduling. So this might be a great opportunity for if you're sitting in the audience and thinking, like, my subscription doesn't have this and I want it, this might be a great opportunity to just copy over and rebuild that subscription as a new one, turn the old one off, and, basically set you up with a new, subscription that's sent out on a regular basis. And that will allow you to do that. But, anyways, jumping back into our subscription, you can set time of day. You can set some of the same settings as before. A great example might be I have a report every week that I'm supposed to go out. Maybe I don't want it to send if it's blank because there's nothing for people to focus on. I can say don't send this report if it's blank or always send even if the report is empty. I can do the same things I did before, including in this instance, I've recruited or included a report that exists in my app. That's my prospective customer pipeline summary report. But I could send whatever kind of report I want, and I can write in messages here as well, give people instructions, give people guidance on what they should be doing with this information, allowing me to get my team rolling, either super fast if I'm focused on something like a record change triggering off a workflow or just keeping people thinking about my aggregate data if I'm doing a daily with, all new tasks or a weekly with all new customers or once a month with all of my closed projects from the month. Or I could even do yearly. It doesn't happen as often, but I've helped some customers in the past who are like, every year around tax season, I need to remind everybody that there's projects that they need to close. Or every year around the end of the year, I need to say, hey. It's the end of the fiscal year. If you have any open budget request, you need to go in and close those out or they will just be ignored. It can be really easy to forget you have those notifications, but, basically, you can go in and make sure that they're set to go out to folks and give people the directions that they need. And then, basically, this will exist on every single table you have in your app. So every table gets its own set of notifications. As I mentioned, you can turn them off, turn them on. You can copy them. You can delete them. You can see who they're owned by, and those notifications will work off whoever owns the notification. So my helpful tip for a lot of people is if you run a lot of notifications and someone leaves your company or someone moves out of position where they're managing the apps, double check and make sure that all of the notifications you expect to go out have an active owner, that they aren't they aren't owned by somebody who's left quick quick base for you or has moved on to a new department. It just to make sure that you have everything running as smoothly as you'd like. And then lastly, if you're wondering, like, okay. I've got a number of tables. Perhaps I have a number of notifications. How do I manage them without clicking everywhere in my application? You can actually go in and under app management, you can find all of your notification subscriptions and and reminders regardless of what table they live in. And this can be helpful for if you know a notification somewhere where you can't remember where. And so that is just a quick overview of how you would build record change notifications and subscriptions. By default, most of you will will be sending these out to users who exist inside of your applications. But perhaps instead, you might want to send them out to folks in a specific role in your app. You might wanna send them out to folks who are listed in an email field you've included in your app. Those options just basically just to allow you to turn record changes and data in your app into a workflow that would trigger for folks. And so I'm gonna stop my share here and jump back into our presentation, and just share a couple of, like, quick tips for using email notifications, sort of getting the most out of them. The simplest one is think about the type of email you're sending that, hey. I would really like this to happen fast. I would like to kick this work off workflow off quickly. Kind of like I mentioned before, I have a sales rep or I have a tech support rep who has to reach out after whenever someone puts a case in and they I want them to reach out really quick, I would probably wanna use a record change email. Other side of things, I have a workflow that's more about reviewing, and it's more about I want someone to look at a bunch of stuff all at once and think about it, make changes. That might fit more with the subscription. And so you kinda have those two options to help you juggle and figure out, like, what should you, what should you be doing to to send that email to folks, what you should be triggering off of. Next is the title. It's a often ignored but super important part of the the email game. Make sure your title makes sense to the folks you're sending it to. Talk about the process that it's kicking off. Talk about what changed. If possible, include field tags that will make those emails informative just by seeing them in your inbox. You know? I could have a email that says you're assigned to a new customer, or it could say you're assigned to, Global State Company Incorporated, and it might be that for someone that will trigger the greater urgency, the right piece of information. They're gonna know a little bit more about that email even before they click it, which will help you make sure they don't miss it in their inbox. Next is the content. So by default, the emails can be pretty sparse. Sometimes it's great to send an email that has two that has two sentences that says, hey, John. I'm reaching out to let you know you've been assigned to a customer. Please make sure you schedule your call. Here's their name. Here's their number. Thanks. Other times, you may want more information. You can customize it as you need. Think about what information would help the folks getting the email take action. And in particular, think about if it's going to your internal team who should just sort of know how things operate or to an outside team where you might wanna do things like add your logo, add some more details or information, add links back to places that they need to access data. And then lastly, control your volume. It's not about, using all caps in your emails or anything like that. This is more thinking about, like, if you're going to be using these record change notifications that trigger off every time something is modified or added, Ask yourself how often that happens and if you're going to be over emailing for a particular instance. Are you do you add a new support case every five minutes, every ten minutes? You probably don't wanna send every case to every rep then. You might wanna start filtering down and think about how do I send cases only to when people are assigned? How do I send cases only when it's urgent? You wanna kinda think about how you control the volume so that the person who gets the email thinks, this is helping me move forward, not thinking, oh, gosh. This is the twelfth email I've gotten in the last twenty minutes. I'm stressed out. So those are just some quick helpful tips for, like, when you're thinking about your emails, how do you make sure that they are moving you forward, not creating, like, an overflow. And so that's talking a bit about our notifications and subscriptions that you can build. There are some other email options that even some pros might have missed or might have forgotten about that are really helpful for, sending a quick notifications or keeping people's interest. Firstly, is personal notifications. So when we talk the notifications we just talked about need to be built in your app by someone who's an app admin, who has the permissions to build the app. So and they need to figure out for this workflow, I need this to go to everybody or a specific role or a specific person. Even when you aren't map admin, you can still set up notifications just for you using personal notifications. You can set them up to keep track of record changes. You can set up subscriptions. You can keep create personal notifications and find any you've already built under your user, drop down menu in Quickbase. It's just in the upper right hand corner where you see your initials or the initial of your user. Drop down, there's an option for personal notifications and reports. This is really great for if you've been invited into another app and you're not the admin and you realize I would like to keep track of something in this app for some period of time. A personal example that I can use is there whenever we have launch season, I'm always really conscious of what stuff is coming out for our launch content wise. When we had an app to help us track that, I put my I put my personal notification that said, let me see or notify me anytime a new piece of content is added to this app that is specifically related to the launch. And I we had a field that marked that for me so I could basically say, just email me when something new gets dropped. And someone wrote a blog article, I immediately get a ping that says it's live. The bonus for this, which is really nice, is you can empower your end users to do this for themselves as well. So if you have folks in your account who might need to track things for short periods of time or may just want their own control over what comes to them, Managers might want the ability to track specific things that there's something on their mind. I wanna track every case that comes into a specific employee because they need more coaching. They're brand new. But I probably don't need this notification forever. They can feel empowered to do that themselves, making it feel like they have a lot more control and saving you as the app admin a lot of time. This is very similar to users being able to build personal reports. As long as they have the right permissions to see and view things, they will be able to see and view and build these notifications for themselves. They're useful as an app admin if you just wanna build something simple. They're useful as an end user if you wanna just keep track of a workflow. And the next is the email to option. You probably seen it. You probably ignored it. I think most people do. It's something that's always super useful every day. But if you are looking at a report or you're looking at a form or a record and you realize, hey. I would like to send this information to somebody. I think for many of us, we think, okay. I'm gonna go into Outlook, open up a new email, copy and paste information over, and then it kinda becomes a bit of like a, okay. I want you to post this thing paste this thing over this whole report or take a screenshot. With this, you can basically just, go in the upper corner of the top of your menu bar when you're looking at a report or form, either hit the email button that shows up or grab the little, more dot dot dot menu and select email. And you can shoot that report or that form directly to another user in the app. So you could say, hey, Colleen. I need your attention on this particular report. It is an example. It is our recently closed customers, and there's way more people on here than I expected. I need you to help me figure out, like, how how are we gonna get enough people, ready to help all these new customers. Alright. And so this is just a quick easy way to send information out to others. I it's the you don't have the customization available as you did for some of those options above, but it's also really set it in for data. Send the email, call it a day, go back to what I was working on. It can make things really simple. Even if you have to do a follow-up through Slack and say, hey. I just shot you this email. I'd love to talk about it. I shot you since you sent you this report, it kind of decreases the amount of stuff you're juggling or looking for or hunting for links over and over again. So that's covering email. Now we're gonna talk about document creation. Like I said, this was added last year. And, basically, what document creation is is it's a feature that helps you take your data. And just like with notifications, we could turn them into emails. This is turning that data into documents. So you there's a simple web designer that you can use to layout your template and generate PDFs, Word, or HTML documents based on your data in Quickbase. It can pull in text and images, references from your field. It can pull in embedded reports from your records and more. There's a lot of flexibility here for you to kind of build what makes sense to you, that allows you to keep track of everything going on. So when you're building it, it's not too difficult, especially if you're familiar with building documents before. You basically go right into your table settings just like we were talking about doing for notifications. And just below notifications, descriptions, and reminders, there's a documents tech template option. And from there, you can create from scratch or import from Word document that you like, purchase orders, task forms, checklists. Anything that you can design, you can build, and you can then put in your logos. You can put in field references. So, for example, if you're sending out an invoice, you could have an embedded report that pulls from a company's table that shows all of the, like, products they've purchased. Or you could have fields that tell you their address, and you can have the address on their purchase order. And so what's nice is you can combine the ability both to put static text that you put in one time, headers, your own company, email address, and and physical address, anything like that that you'd wanna just put on the report and have it appear every time. And then you could put dynamic information here, set your page time, change your margins, set your layouts, and you will be able to generate this document and use it. This thing might be wondering, like, what, like, how do I use it now that I've generated it? There's sort of two options. You can either use a formula button from our exchange. If you go into the graph exchange and look up document creation, there's a little button that basically when you click it, it will generate the document for you. It'll pop up and you can save it so that you could then attach it to your own email, send it to someone in Slack, print it out, and hand it to a person in your office. Or going back to the emails you're just talking about, there is an option to generate and send a custom email using the new custom email option that I was showing you before, the the build your own at the very top, and have a a document included when you send that email. So you can send an email that says, hey. Your project has your bid has been approved. I would like to, to take take up your offer of work and pay you to come out and do a project for me. Here is, a breakdown of the work that I want you to do. Here's the contact information to get in to get, work set off for me. Here's the timeline. Whatever you wanna send out, whether, like I said, it's an invoice, it's a PDF of location information. And you can even use this with our, APIs, generate a document through pipelines and through other automated systems. That's just the more advanced option that kinda takes you off roading, if it if you will, for everything. And just gonna think about, like, documents are all around us. These are just some examples of that I was talking about already, but, like, vendor management, new product development, quality control and compliance, production planning. These are all instances where you may already use a paper form, and you might be filling it out by hand and constantly repeating data over and over again or, you know, if if like me, you have bad handwriting, having to go very slow and make sure that your form is legible. These are options to to replace the, the the more manual processes with scalable digital processes. And these things can then be shared, saved places, basically just simplified, to make with what makes sense for you. So by default, I saw a great question from Robert that I think is really relevant for what we're talking about right now with the will documents be saved in a file attachment field? No. By default, when you generate the document or when you send the document via email, that is, like, a one time and it just happens. That's where things like pipelines can be helpful. You could set up a pipeline to save it somewhere and say, I generated this document, save it. Or you yourself can show display it, save it to your computer, save it to a file attachment field. That's just because this is the kind of thing that can happen, like, on the fly. It might be that I would hit this document 10 times in the course of a week, and it would change regularly. We just don't have to save it every time. Yes. So and that's a great question on availability from Delisa. This is available on our business and enterprise plans. So basically, the not on team. But if you're on team and you're an account admin, you can request a thirty day trial. So if there's something you would like to see before you commit to, and kick the tires on, you can trigger, if you go into your admin console, there's an option to trigger a document creation trial. Or if finding it yourself in Quickbase is daunting, you can always reach out to our tech support or us for help on setting up a trial for it. And you will be able to, basically pull that out, and try document creation even on a cheaper. So it's tryable for anybody. It's just available for everybody on business and enterprise. And then moving on, making sure to just keep in time. I guess, we're gonna talk about sharing your app publicly. And you we're thinking a little bit about here about, you know, first, we talked about sending e emailing data out, then we talked about generating documents with our data. What if I just kind of wanna make it simpler for people to get into my app and see my data? In particular, is there certain circumstances where I wanted to share my app publicly with users who don't have access to my Quickbase account? We realized adding everybody who needs to see data as a user could not be the right fit for every use case for Quickbase. Instead, you, you might want to say, I have this workflow where there's a report that lists all of my events this month. I actually don't mind if the public sees this. I would make this events app that I have. I would make part of it public to everyone in the Internet so that that email can go into my documents, can go into my emails, can go on my website, and no one, would have to go in and do the nitty gritty work of adding a user or emailing this out every time it happens. To help with that, we created a special group called everyone on the Internet that you can invite into your app, giving anyone with a link to the app whatever permissions you have assigned to this group. Plan question came up about the last feature. I'll cover it really quick again for this feature. Anyone who's been on Quickbase for over a year, you, by default, will have access to everyone on the Internet even if you're on a team plan. Anybody who's a newer customer, who's brand new, may not see that everyone on the Internet option available if they're on team. It is now on business and enterprise for new future customers. But if you're on team, you're grandfathered in, you will still have access to the ability to use this. But, basically, what this does is you invite it just like you would invite a user, and you give it a role in your application. And So you might be thinking like, that sounds great. Like, what's the catch? Why would I just not do this for everybody? And what it really comes down to is security. You wanna ask yourself, who do you wanna view your data? With only logged in users, you get maximum security. You pick a user and say, Evan's only allowed to see the things I've given to the role of a project manager. No sensitive, data goes to him or or maybe it does. Maybe I'm allowed to see financial information, contact information for a customer. Next is something we're gonna talk about later, which is logged in users or people with a secure link, which is kind of like a middle ground between this. And the last option, anybody, is when you set things everyone to the Internet, if someone has that URL, they can see it without signing in. If you make it so that a workflow can add a record, for example, like, really common use case for this might be I have surveys that I want customers to fill out, and they can be anonymous. I actually don't mind if they just fill out the survey and say that their experience was a five five, five out of five, ten out of 10, or maybe one out of five and they have notes about why they didn't enjoy themselves. That's fine. But it does mean that anyone can put that stuff in. And in particular, if you're sharing data, that same example of an events calendar, you probably don't mind sharing a calendar of your events that people can register for, but you probably don't wanna share your client list or you probably don't wanna share your list of active projects with the dollar amounts attached to them where anyone could find it. And so thinking about, everyone in the Internet, we always recommend think about it for workflows where you wanna make it simple for people to see data or submit data, and you wanna build a role for that user that makes sense. You can build a role that's just able to go into an app, submit a survey, and they can't even see their own survey because it doesn't matter. They've they've sent it off to you. It's now gone. We probably all think about instances where we would submit feedback to a company, and we don't need to see anything back. So some examples I've already covered, but some other ideas might be like surveys, feedback forms, appointment requests without needing to sign into Quickbase. Maybe a vendor of mine can just use a portal to submit a request that says, like, hey. I have a con I have a a a concern or an outstanding bid. I'd like someone to contact me back, but I they don't need to see that information. We'll email them or call them. Subcontractors, great example would be I may have a group of people who can take jobs from me, and I just want a list of my available jobs for them to bid on to be visible. I can make sure I don't include any sensitive data there. I could just include a list of, like, these are open jobs that I'm looking for people to to fill in for. Low risk, nothing sensitive, just kind of giving people an opportunity to see stuff. And there's a flow for them to reach out to me, submitting a contact request, submitting a feedback form. And then on all of the above, you might have some file attachments that you've included in your Quickbase apps. For example, like, you have a a document you generated that lists your events for the next month, and I'm gonna fall back on that events example. You could just make it so that that, file attachment table and the links to those file attachments are available to everyone on Internet. So someone could just open up the file attachment from a link. It's really helpful for some simple workflows. And there's just basically the steps to set that up. You're thinking of it very similarly to inviting a user to your app. You choose the you go into your users table, select share app with new user, select a little address book icon that appears, and you're gonna be looking for that everyone on the Internet in the drop down of options, or you can type in everyone on the Internet and we'll kind of search for that for you. You're adding them to your app, and then you're thinking about what you're gonna match them to a role that makes sense. And what's really helpful is if you're not sure what all a everyone in the Internet user can see, open up an incognito tab, open up a private browser, go into a different browser where you're not logged into Quickbase, drop the URL to your app in, and see what you can see. And that's a really great way to see. Like, if you see anything you're not supposed to see, that's a great, like, flag for you that you need to go back and look at that role because you're maybe not ready for that user to have access to that data or that part of that app. But you can tailor the role that you put folks in to really match what you'd like them to see. And this gives you an option to sort of have your apps be a little more accessible, have new avenues to add data without having to add every single user because that's not always feasible in every workflow. I might not want to add every person who one time stepped into one of my businesses and giving me a survey on their experience. And then lastly, I kind of referenced this a little bit earlier and I talked about a little bit more. We're talking about secure links. And so what secure links are is they are tool for giving nonpublic information to someone who isn't a user on your Quickbase account. So with our share sharing with everybody, we talked about before. Anybody could see that they kind of had this link, and it sort of just exists out there in the flow. These secure links give us a tool to help control what they what folks can see and where. In particular, they're really great when we think about, like, I don't need to share sharing my code makes my data easier to find and my data that any data that I email is static. A secure link puts another layer of protection between, a user out on the Internet and your data, but allows them to see up to date data. Whereas, like, if I email this data out to somebody, it might get stale or outdated. They could come back and reference it again. And sort of on our word for security, our little security scale, it's the medium sized lock. It's the they're logged in with the SecureLink. It is more secure than everyone on the Internet. It can't just be stumbled upon by accident. They have to have a particular, access string to get in. And so, you know, what can I be using SecureLinks for? For? Similar to what we're talking about with the other things in today's presentation. It could be support cases and a ticketing app or I need the customer not only to be able to submit the case but see updates as they happen. It could be vendor bids including details like pricing and contract information where I want the vendor to see as we're updating the record what's changed. It could be details about sending work orders as photos come in as the updates happen. I need to just have stuff to come out. And so we talked a little bit about, like, how could this enhance my email notification? Because we can actually use secure links in our emails. And we could have a example where, hey. With your bid with share publicly and email anybody, I could they could submit a bid to me, and I could send an email back that says, like, thank you. We've received your bid. Here's the details of what you submitted to me in this email, but you cannot go in and change this bid anymore. Flip side, if I'm adding secure links to the to the flow, I could say, thank you. You submitted your bid to my publicly facing web page or my publicly facing app. Here, the special link that I'm sending to Jess to you that lets you modify your bid and not anybody else's bid, just the bid that that matches this link. And that allows you to have a workflow where you're not really stepping in to add these more like, you're not stepping in to send every single link to everybody. You're using the systems that already exist to give folks the opportunity to come back in and edit their bid, edit their survey responses. And you can even use some tricks to help you figure to to because this lets you use permissions in Quickbase. You can say only for a certain period of time. After the record exists for thirty days, I could set it so that it does it no longer allows them to edit records anymore or view records. So there's more control than that available to everybody because the, the secure link gives you kind of like a key and you can revoke that access. So secure links are made up of three key components. There's a URL that gets created and includes an access key that you send out, whether it be an email, a Slack message, however you wanna send this data out, an email outside of Quickbase. Then the next part is there's a formula field in your app that is looking for that access key and helps your permission say, if I don't have this key, don't let me see this record. And then lastly, there are the permissions you set up to control record access with that key. And so if we're just talking about, like, from a technical perspective, there's a plain old URL that someone will have that has that access key attached to the very end. Or you could even have a URL with a redirect. You can get fancy. And what it might show up for them in an email is, like, this text linking to the URL. It could just say click here, edit your bid, or even could be a button that says edit your bid that you throw in one of your email notifications in one of your documents you created if you need a PDF. And this just helps you control the experience of accessing data. Who can use the link? Important thing to know here, if anyone who has the link or was sent it or forwarded it can use it. That means it's not a 100% foolproof. You can't say Only this one person is ever able to use it if they share it with somebody else on their team. If they share it with another person at their company, that person could also access it, which is why sometimes you wanna think about time limit. They could edit this bid for a week, but then after a week, I wanna cut them off just because I don't want things to get further out. Yes. Yeah. So that's the end. So, basically, this what I'm gonna do is a quick demo where I'm walking I'll walk you through an example of what it looks like to have one of these because it's a little, it's a little hard to conceptualize all the pieces. Jump into Quickbase really quick. Yes. Share. So what you'll see here in my complete project manager app, I may want to set it up so that folks could see a project. My vendor could see a project that I've assigned them to so that they can come in and update important information. And so we're gonna find quickly the pieces of our secure link. So I have an admin section here that generates my secure link for me. If you're familiar with all the Quickbase formulas, it is using a Quickbase formula where it says take a bunch of pieces of information, including the record ID, the date it was created, and I'm using an example where I include the email of my vendor to help me focus and narrow down my access just a little bit more, and control. Can they see this date? Because, basically, this is going to generate the link that I would send to somebody. And then I could add this field into an email notification into a document I've created that will send out. So it says, I so for example, I'm back here in my complete project manager. I can set it so that it goes out to whoever I've put into this vendor email for secure link. So my own email put in here for example, I could say, okay. Whenever, this email gets added, I would like it to go into my formula. And or I would like to go into the I would like to, set up the email with the formula so someone could have a link to it. And what's really helpful is as an example of my link, you can see I have this other formula field here that is using a Quickbase formula to look for the link. Oh, yeah. I can show you an example of that as well. Sorry. I didn't realize it didn't show when I did it the first time. Let me just share that screen too. Here is an example of what the formula looks like. So you can see there's a section here that basically creates the access key in for you and then turns it into a URL. Don't worry if you're not a Quickbase Formula Pro. This might not make sense to you. You can also always find this formula on our app exchange. So when you're in Quickbase, if you open up a little waffle menu in the upper right hand or left hand corner and click exchange, and you just search for secure link, there is a formula that you can add into your app and there's a little wizard that will walk you through adding it into your app. So you can put a secure link wherever you need it. I frankly got this formula from the exchange myself as well because hopping and pasting it all over the place drives me crazy. And it will come default with record ID and date created to make it, like to help make the key. I often add email address because it's just an extra piece of information that can help control the key. And I'll explain a little bit more why in just a second. And then let's go back into our flow. So So let's go back into your error record. So I have set it up so that the email becomes part of my code. If I ever go in and remove this person's email and I save it and I take a look at it, their code will have changed. This will have updated and become shorter. That's really helpful because if I ever sent this code out to anybody, if they go to use that code that's in their email, it will now be an outdated code and it will no longer work for them. And how that happens is there's another formula field in here that uses a new formula function we added that checks for that code existing in the URL. So all I have to do to get this checkbox to look checked is to use my field, and it can see that in my URL, which doesn't show up on the screen, but it's basically right above, it now includes the access key it knows. And that's what I build all my permissions off of. So when I build a role, I say only let them see records and edit records where that access key valid is checked. And so that means they can't see anyone else's record because they don't have the access key, but they can see the record I gave them access to. And I can basically trigger that anytime I'd like. And I'll give you an example of what it looks like real quick when you send that email. So this is an example of what it looks like when they get the email on their side. It says, you know, dear Evan, you've been assigned to vendor contact for one of our joint projects. We need you to update your project with the plan by this Friday. To access this project, use this link. They would click that link. It would open that record for them, but only if the access key still match the access key on my record. So that means I can I have control to revoke access when it makes sense for me if I need to? I can also add simple things like I only let them edit records if that checkbox is checked and the record isn't older than a week. Then that way, for the first week, they can edit their record, but after that, they're locked into their final answers. And that's just a simple way for you to think about using the, the workflow, for you to make to be part of your workflow for controlling your data, giving you a little bit more control. And so setting up a secure link, this was just a demo of me walking through it. We have tons of documentation that will help you. You can think about it as first thing you do is you open your app to the public. You get that EOTI rolling. You add the formulas that are in our exchange to your application. You build some permissions that use those formulas. And then lastly, you would create that notification. So whenever a new vendor is added to a project or a new customer is added to a tech support case, they would get an email that says, hey. Here's your link specifically. This is basically the program. Like I said, between it's open to everybody or you have an assigned user. This is sort of like, I have some control over who gets access to my data. Alright. So we're coming up on time, so I wanna move to q and a. Thank you, everybody, for your time. We're gonna jump into the questions that I have access to have available here. Let's see what we've got. If it's a secure link and add to a project. K. So I've got if a secure link is added to a project and sent to a customer, can that give them access to a regulated task or is that another secure link? That is a great question. So what's nice about secure links with them being, formula fields is you could pass that information down. So you could use a lookup field that looks that formula that that access child records, and you could use that same permission on that table. So you would wanna set it up that they could see any records, let's say projects and tasks. They could see any projects and any tasks as long as they have that access key. So you can cascade the permissions down a little bit. It's a little more complicated. If you're not something you're familiar with, you can definitely get help doing it. But, basically, you can, let them see more than just a single record with the same access key. You just have to pass it through the relationship. I'm gonna here. Is there a way to make access key time based only able to be used for a specific time period? Yes. That is a great question. That is where I typically lean on the permissions of my application. I basically set it so that, a specific record maybe has to be edited within the first seven days it was created, or I can even set a date. This is, like, for this person in this role. I have a a formula I have a field on the record that says, like, must be edited by the January 31. And if they are past that date, the permissions will say, hey. Even though you have the secure link, sorry. You can't see this record anymore. And that'll give you the ability to control a little bit more. There's also options like what I did including an email address as part of it. You could put some kind of piece of, piece of logic into the formula so that the formula itself will no longer match their access key if a certain amount of time has passed. It's a little more complicated, but it's something you can do to sort of bake in a little more protection for yourself. I see there was a question really great. Someone asked, where can I find this video again in the future? There'll be an email going out to folks tomorrow with this on demand. You can always find it on our events page on demand. Also, if you, look for if you wanna learn more about Secure Links, there's also a great video where it covers a very similar demo to me on our YouTube as well. If you click if you Google Quickbase and Secure Links, Charlie from our team kinda goes over the same thing. I went over today in his own demo. You can watch at your own leisure. You can watch just that part if you'd like. His video is much shorter than this. And let's see. Any tips for doing a biweekly or repeat? So you're thinking, I don't want I want this to send every two weeks instead of once a week, or I want this to send, or I want this to send twice a week. Either way, sometimes that's just a matter of having more than one subscription. You could build a subscription that's sent at the beginning of the month and then build a subscription that's sent on the third week of the month, and that would kinda help you get to biweekly. Obviously, it's not perfect logic if the way that the months are split. Alternatively, what I've done in the past is set up a weekly report. And as part of my filters, just pull the formula formula field in there that only shows a checkbox on the weeks that I care about. So every other week, it'll show a checkbox. So then you'll just get that blank report on my off week, and then nothing will send out. It's a little less smooth than using the weekly or monthly options right out of the gate. Simplest is potentially just build a monthly report twice so that you send out more than once in a month. And for all intents and purposes, it will look the same, but we'll be running on a different logic. That's everything I have in my q and a section. Let me go through the chat really quick and see if there's anything I missed. To see from Danielle, I have, for document creation, if I'm generating from a parent table and wanna display an embedded report for a child table, can I query filter the child table to only show child records related to the parent? Actually, great. If you use exact forms before, you're probably thinking I have to add a query. If the form includes an embedded report, that embedded report can be pulled into the form without having to include a bunch of filter logic. It is pulling from Quickbase so it will know I have this project, record form and it includes an embedded table of tasks. It will pull that information in as well, as long as you build it using that you just as long as you build it that way. So you don't have to build a special query or know the special code for it. That was something that we thought about when they built document creation. It's definitely the kind of thing that, like it's nice. It's nice when you can just kinda send it and know that the records will go. I see from Joe, after adding a new record, can I redirect an anonymous user to a Quickbase app page and show the secure link to add and show the secure link to edit it? That is a great question. Yes. I believe since it's in there, you would have to just redirect back to the form after it's been saved because that won't be generated correctly until saved. Because part of the secure link logic uses the save date of the record or the creation date of the record, so you would have to redirect them back. Maybe not. I think the easiest is usually in my experience is to send this, like, a generic thank you page that drives then lets them know an email that's coming with a secure link rather than trying to show on the screen. So I think you're gonna you would have to build some complex logic to get it to show up because there'll be a point in time where they don't have permission, so they wouldn't be able to see that link or that link's floating out there in the universe and someone else could theory find it. And let's see. What else do we have in here? As a reminder, the formulas I referenced today for exchange are for the, secure links are in the exchange, including I also linked in our document section, the help article that walks over setting up everything we talked about today. So there's help articles for document creation for the exchange. I see someone asked about, can you generate documents from a template in bulk rather than one per record, like making all of the invoices generated this week in one PDF? Yes. The easiest way I know of is you can help use the help of pipelines to generate multiples. You can also get fancy. So we use a button to call there's a button you can download from the exchange that basically generates that document. If you feel fancy, you can kind of set it up so that you can use some, custom coding to build a button that pulls multiples at once. That's just a little beyond the the realm of I'd have to sit down and think about how to do it if I was gonna do it myself and probably trial and error a few times. It is possible. Let's see. Is there anything else in here? Someone asked if there's a record of the email being sent. As of right now, by default, there is not a record of the email being sent, like, in the email itself. If you use audit logs, we did recently add the option to get better availability better visibility in our audit logs into email triggers. So audit logs are a way to see this information, but you have to use the audit log feature filter for the right kind of events. Something a little out of scope for today, but, if you look back on last month's, future focus, I did talk about it a little bit there. How to access analogs. Alright. So we've come up to our time at two. Thank you all for joining us today. I hope you found the session useful. If you still have questions, do not do not hesitate to let us know and feel free to reach out if there's something that you need help with. As always, you can feel, feel free to reach out to our tech support team at any time. If there's some questions you have need help with, they can have gladly point you to documentation. Otherwise, you will receive be able to access this on demand as well as all of our other demand content on our events page. And if you're looking for another session in the near future to help you continue to build your Quickbase skills, on the thirty first, we will be running a formulas one zero one, which will dovetail really well with having to learn those secure link formulas, but we'll cover the basics of formulas. How do you access, how to write them, how to read them, how to start building your own. You can find a link for that in the doc section, or, again, you can find it on our events page at quickbase.com/events. Thank you very much for joining us, and I hope you have a great rest of your day.