Cory, Steve, Sean, and I touching base on a number of different projects. We started out with some questions on connecting to special hardware and what those configurations need to be. At some future time, we may need a hardware expert to join the team to help with setup and configuration between hardware and the web. Sometimes that gets kinda tough. The web doesn't do much there, most of the tweaks and changes come on the device and through small applications loaded on the system or through drivers or something like that (little mini apps and settings).

We started talking about settings and permissions. A client wants to allow a person (user) to go to a certain place (say timeclocks or timecards) and not be able to see certain things. This topic spun us off into a small discussion about permissions, settings, functions, and even sub permissions. Eventually, (we know that is a bad word) we see the permissions being a combo of both settings and permissions. For example: Say the main permission deals with something like timecards or timeclocks. Then, deeper, inside the permission, there may be sub permissions or settings. Eventually, all of the functions of that permission may need to be available for or part of a sub selection. Both settings and permissions may end up being combined and will make some sort of hybrid type system at some point. Just looking down the road a bit. Just for fun, there is another example: Say invoices - within in that, you could have functions like add, edit, void, remove lines, make payments, searches, limits, histories, exports, etc. It can get deep really quickly.

We worked through a small quote for a client dealing with some new permissions. Part way through, we had to fix a small error on one of the pages. The new permission was dealing with show/hide options for salary and wages being shown on the timecards and timeclock records. As we got deeper into it, we found that the manager's permission already hides those pieces but the admin timeclock stuff does not. We did the quote and got some options ready for the client.

We switched and talked about some feedback from the  conference. We talked about getting buy in on some of our future plans and pieces by pitching what we've got. After that, Steve and Cory were batting a few things around dealing with other projects and follow-ups. Cory has been amazing and is doing a great job! Huge thumbs up!

Here are some other small things we chatted about: They got into talking about vendor types (small flag for vendors to be either expense vendors or inventory vendors). Reports, exports, and being able to save certain reports. We flipped back and forth between the conference, upcoming plans, and fifty other topics. Just for fun, Cory was saying that she got a bunch of good feedback from the clients who were at the conference. We, as a team, are a pretty crazy machine when people see us in person. That is kinda fun.

We then talked about scalability and how things like alignment, balance, projections, and confidence play into the mix. Cory was saying that she feels like the things that her yoga instructor tells her about herself apply to business and our adilas team. Good stuff.

The final topic of the day was an MVP (minimal viable product, plan, person) on the payroll side of things. A new facelift, revamp the clock in/out section, and make it a standalone mini project (gateway or doorway into the bigger system - the teaser section). We would love to revamp that little project. We then talked about how to fund that and how to move forward. Making plans!