# Oddities with Multiple Companies Thanks everyone for the thoughtful feedback, this is really helpful, and I’ve shared it with our team. At the moment, the client experience is designed so that each company has its own separate view, which means we can only support one Files channel per company/user. A fully consolidated view across... ## Clarification Needed Sorry for the delay [@Andrew_Lowe](https://community.assembly.com/u/andrew_lowe). To make sure we fully understand the pain point, can you clarify why the current setup is problematic for your clients? Is it that the separation between their personal, company, and trust information feels confusing, or are clients not noticing the switcher UI on … ## Feedback on Use Case Hey [@Andrew_Lowe](https://community.assembly.com/u/andrew_lowe) thanks for sharing your feedback. Your use case makes sense. We work with many accounting firms that handle a mix of personal returns, multiple companies, and trusts for the same client, so we’ve seen this scenario come up before. One approach that’s worked well for other custom... ## Bug Notification Hey Dave, sorry to hear about this. Our team will take a look. ## Portal Notifications Yes you should add the suggested record. Remember to use the mail name so that this SPF record is associated with the subdomain and not your root domain. That is the key difference here and why this additional SPF record is not a problem. So in this case, you are not adding multiple SPF records to t... Thanks for sharing the screenshot. I can see on the left-hand side it shows “@”. That means this TXT record is connected to the root domain. You will also need another TXT record; the name is mail, and the value is "v=spf1 include:amazonses.com ~all". This second TXT record will be separate and wo... Hi [@Andrew_Lowe](https://community.assembly.com/u/andrew_lowe), since you are using a custom domain you will need to add a specific TXT record to verify SPF is aligned from AmazonSES (which is the underlying infrastructure we used to send emails). Try adding the following record: Type: TXT Name: mail. Value: "v=spf1 include:amazonses… ## New Portal Account Creation Hi [@Ayman_Bahta](https://community.assembly.com/u/ayman_bahta) thanks for asking this question. There is a setting to disable direct signup. You can read more about it in our [guide here](https://www.copilot.app/guide/client-direct-sign-up#enable-client-direct-sign-up). With this setting turned off, there will be no sign-up option and you will have to create clients for them to be able to log in. Hope you found this answer helpful. ## API Key Issues The “token” you have created called decode is a new API Key that is not the same as an app API key that you need to decode a token passed to the app. To create an API key for the for an you want to follow the [setting up your first app](https://docs.copilot.app/docs/custom-apps-setting-up-your-first-app#step-2-register-your-app-and-get-an-api-key) instructions and use the API key generated here in your env vari... I deleted the second message you shared above because it showed your API key in the error logs. Based on what you’ve shared above, the issue you are facing is very likely that the API KEY you have set in the env vars is NOT the same as the API key for this app. Each custom app you add in your w... Thanks, a few things come to mind. Can you share how you are calling this endpoint that you’ve set up? Specifically, I would like to confirm how you are passing the token in the request body. Can you confirm where you got the value for the API key to set the env var value? If the token is passed in... ## Token Clarity That’s great to hear that you were able to decode the value. The approach you describe is exactly what I would suggest. I’m not sure what you mean by just a static token. The token that gets passed to your app is generated dynamically using the API key for the app. If you are finding that the token... [@Farah_Abdulwahab](https://community.assembly.com/u/farah_abdulwahab), you’ve got the right idea here. One thing I wanted to confirm is that you have set COPILOT_API_KEY env variable to the API key that was provided at the time you created the app. If that is not set or is using a different key you will get an unauthorized error. Essentially... Thanks for clarifying this. The token you are seeing in the docs is an example; the length will not always be fixed and has some variability based on the token payload. The easiest way to decrypt the token is through our node SDK. Have you tried this already? Using that is one line to get the token payload... Hi [@Farah_Abdulwahab](https://community.assembly.com/u/farah_abdulwahab), thanks for asking. Can you clarify which documentation you are referring to that specifies the length of the token? We would be happy to take a look to understand what might be going on here. ## Magic Links Question Thanks for the suggestion. I agree that would be better. I will pass on this feedback so we can make this improvement. ## Payment Capabilities Inquiry Thanks for asking this question. It sounds like what you are asking for is the ability to support partial payments, and that's a very valid request. We’ve seen this feedback before, and it’s a highly anticipated improvement on our roadmap. We don’t have a timeline for it quite yet but no doubt something... ## Security Inquiry Hi Andrew, great question. No login link gets sent in that case. That is intentional for security purposes. If we were to show an error like email doesn’t exist, that would expose information about your clients to a bad actor. Someone could try to guess various emails and then figure out which emails... ## Email Notifications Hi Andrew, yes you can disable this. From the sidebar if you go to “App Setup” and edit the Contracts app, you will see the following page You can turn off “Email notifications contain pdf attachments” and hit Save. ## Future Vision Hi Kyle, great question! In five years, I see Copilot as a foundational operating system for client-based businesses. Today, we help consolidate the scattered tools and workflows companies use to work with clients, but that’s just the beginning. Fast forward, Copilot becomes an intelligent, adaptive... ## Platform Updates Thanks! Great to hear the platform made it to your favorites; it’s a core part of how we think about extensibility and customization. We recently rolled out major updates, including new billing-related endpoints, and there’s more on the way: - Tasks API: We’re expanding our API surface with endpoints... ## Community Welcome Hey everyone! And hello Discourse! Hey Otis, excited to have you as part of our community!!