As you work through your first several weeks or even months in the Digital team you will doubtlessly find questions, terminology, or process that is unfamiliar to you. This FAQ answers some of the most common questions asked by new hires, and gives links to some of the most important resources for new members of the group. If you have a question that isn’t answered here, ask it in #org-faq in Slack. Questions that may be useful to others will be added to this document. Feel free to open a pull request if you have something to add!
General
What is the Banno Group?
JHA’s Banno Group works on the Banno Platform, a modern solution for nearly every digital need of financial institutions. This includes Marketing, Content, Apps, Support, and more. As we work in a way unique inside of Jack Henry, we have prepared this wiki to answer questions not covered in your standard JHA on-boarding information.
What should I expect on day one?
It’s funny you should ask that, as we have a page dedicated to exactly that. The short answer is that much of your first week will be spent setting up your machine, meeting your team, and doing some of the required training for the systems we use here. You may need to talk to HR about Benefits or the IT Help Desk about getting VPN setup. If so, you can find their phone numbers in the Phone Book.
What does our organizational structure look like?
Our communication organization is flat, you should feel free to communicate with any team member no matter their position and are welcome to do so. However, sometimes you just need to know who to ask a question or who can unblock you. You can view JHA’s organizational structure by searching for an employee in JHAToday and clicking the tree structure icon next to their name. Or you can look up any person in Microsoft Teams and click the organization tab to show you what team they are on.
Some teams, such as our Data Services team, are subdivided based on the projects they maintain. As these might not be directly reflected in HCM due to the flexible nature of these teams, we use Slack’s User Groups as our team index. If you’re wondering who works on a specific project or feature, or who to ping when you have a question, you can refer to this list. Details in our [User Groups](/guides/how we work/user-groups) guide.
What do I do if I can’t log into a JHA resource?
If you cannot access JHA Today or HCM, there’s a good chance your credentials are locked out or have expired. Send a direct message to @agent_smith with account-status to see the state of your account. For more details check out our guide to Passwords.
Which chat rooms do I need to join?
Our communication architecture guide has details on how we use chat. If you have further questions, ask your team lead for assistance.
What is jSource?
jSource is a software system used for Customer Relationship Management (CRM) at JHA where all client and customer data is maintained. To be able to use jSource, you’ll need to [complete jSource training](/guides/helpful hints/jsource-training). Only a subset of employees need to access jSource. Ask your supervisor if jSource is right for you.
What resources for professional learning are available?
We have a number of resources available for those looking to grow technically or professionally.
We keep a collection of previous tech talks with subjects ranging from language-specific programming overviews to process-oriented How We Work talks.
We have a collection of books for all disciplines, as well as a process to order new books we don’t have on hand.
What is Git, and how do we use it?
Git is a version control system, and it’s our main repository for both code and this wiki. If you are having troubles getting it running on your machine, we have a short walkthrough available for those new to the tool.
We use Pull Requests extensively in our development. As such, we’ve outlined our guidelines for how to commit changes to any repositories you work on.
How do I request new hardware?
If you need new hardware, such as an adapter or keyboard, requests can go through the online self service helpdesk) or by calling the IT Help Desk. This will kick off the process to get the new hardware, which will go to approvals. However, if the result of your case is that the item will come out of our cost center instead of being an approved hardware replacement, Lory Trost will need to be notified before it goes to management approval.
If you need a new laptop, and already have Ground Control-issued hardware, or would like to request that you switch from corporate-issued hardware to Ground Control’s, then you can fill out a Jira ticket here under ‘Computer Support.’ Hardware requests are handled in as timely a manner as possible, but ultimately order priority based on severity of need versus what Ground Control has in stock. If you want to stick with corporate issued hardware, see the above link for the self service helpdesk.
What educational opportunities are available to me?
Glad you asked, check our Conferences page
How do I take PTO?
Instructions on how to take PTO are located [here](/guides/how we work/pto).
Accounts
What are all these credentials I received?
Banno group members have a number of different accounts they may need. A large part of the reason for this is because we have maintained our own ecosystem for email, documents, and deployment. This means we must maintain both our own accounts that we use day to day as well as our JHA accounts for interacting with the larger company. Day to day, you’ll usually only interact with a handful of the accounts you have. The most common accounts created for new team members are:
JHA Account - These are the credentials used for most JHA services, such as BEP/VPN, HCM (Payroll, time reporting, benefits), JHAToday (frontpage news, directory, and access to other systems), and the LMS (training and policies). This will usually be your first initial and last name (for instance, Bullwinkle Moose might be
bmoose). Some services, such as LMS, require appending@jhacorp.comto the end of your username (as in, jsmith@jhacorp.com). If your standard username does not work, try adding@jhacorp.comBanno Gmail - Banno email runs through Gmail. You should have received these details to your personal email ahead of your start date. This account is also how we manage document sharing via Google Drive as well as authentication to view the BannoDocs at docs.banno.com.
With two email accounts, JHA and Banno, you should [manually set up email forwarding](/guides/helpful hints/email-forwarding) during your first week to ensure you receive all important emails.
LDAP - These credentials are primarily used for anything under
banno.com/a/, Jenkins and git.banno.com, our internal github. Most of those in engineering will have this created day one, but other groups may not need it. You can access your account and reset your password via https://ldap.banno.com/.Slack - Once you have access to your Banno Gmail you can setup your slack account.
GitHub - When you join the organization you should receive an invite to the Banno GitHub organization. If you already have a personal account we encourage you to use that, but if you don’t setting one up real quickly is a breeze.
I need to reset or change my passwords. What do I do?
We have a document about resetting or changing passwords here
If you are an hourly worker and you were locked out trying to clock in, you can manually enter hours for the day via the timesheet in HCM. While it will generate an exception that will need to be approved by your supervisor, it’s preferable to not including the time you spend unlocking your account.
Teams
Most of our teams have their own page and up to date description that you can find by starting at the main page of Banno docs. A few of the key groups are; Dev Relations, Engineering (Infrastructure, Mobile, Product), Operations, and Product Design.
Banno Committees or groups
There are regular meetings at Banno organized to support the cultural direction, processes, scalability and security of our teams and services. Current membership can be viewed in the corresponding Slack User Groups and their organizational channels.
Leadership Team
@leadership communicates in #org-leadership and consists of team leads, engineering managers and directors across the organization. This team is primarily focused on the cultural aspects of the Banno group. They are here to help and support you.
Scale Team
Includes a dynamic membership of engineers and static members that include operations and engineering directors, and engineering team leads. The group reviews upcoming customer launches, identifies infrastructure and code changes that affect reliability and scale of our services and reviews systems for capacity constraints. Bi-Weekly Agenda
Security Team
@security communicates in org-security has a static membership and consists of the director of engineering, technical and team leads of infrastructure, CMS platform technical lead, and Data Services Engineer Advisory. This group meets to discuss emerging security concerns, processes, threats and trends particularly as they intersect with Banno.